Actionist Knowledge Docs
Generated knowledge spine · knowledge/03-EVIDENCE-MAP.md

03 · Evidence map

The high-signal source packets behind each current domain decision.

Generated from knowledge/03-EVIDENCE-MAP.md · regenerate with node site/system-map/scripts/generate-docs.mjs

Evidence and prior-work map

This map points to high-signal source packets. The generated source-inventory.jsonl accounts for the complete inventoried tree.

Core synthesis and framework

SourceContributionDomains
Initial research synthesisMarket structure, last-mile failures, atoms, evidence gatesD01-D05, D17
Original first-principles frameworkProblem tree, capability inventory, block contract, lifecycle, eval and economicsD01-D18
Expansion synthesisCompany, GitHub, public-signal, standards and niche joinsD01-D05, D17
Phase 8 synthesisUniversal Block Foundry, local corpus, templates, mechanics and compositionD04-D17
Claude lane synthesisConnectors, Lovable, templates and UI preference scienceD12-D16
First-principles domain mapCurrent 18-domain decomposition and challenged assumptionsD01-D18

Demand, industries and archetypes

SourceMeasured contributionLimits
Industry atom specifications17 industries, 12 teams, 66 use cases, 72 ideas, 12 atomsDemand structure, not validated willingness to pay
Niche→atom→block joinCrosswalk from catalogue to atoms and repository baselineRepository relevance is not capability readiness
Industry contradictionsContradictions and absence codes by industryPublic evidence has denominator and access gaps
B2B template shelf10 archetypes, 17 pinned rows, 34 industry-archetype variantsShelf is a seed, not a production template catalogue

Source discovery and corpus

SourceMeasured contributionLimits
Permanent capability source registryJoins expanded-universe seeds, P03 candidates, recovered Foundry/operator nominations and Bykonz runtime precedents into one identity projectionRegistry status is not qualification or admission; evidence classes remain separate
GitHub expansion report500 unique candidates; 17 industries; 9 capability familiesMetadata/reference corpus
Phase 7 corpus integrity1,700 target rows with 270 complete and 1,430 explicit deficitsCompleteness invariant was research-specific
Pair completion forensicsProved the 270/1,700 denominator and evidence gapsDid not execute or qualify repositories
Local corpus join8,515 UI identities; source/bundle/overlap distinctionMini corpus unresolved
Local corpus block joinJoined local assets to block stages; zero strict Stage-0/admission assets at that snapshotStrict gate outcome, not absence of useful code

Capability contracts and reuse mechanics

SourceContributionLimits
Block Contract v1Full governed capability dossier and synthetic fixtureToo monolithic for composition interface
Universal Block FrameworkPackaging modes, evidence families, lifecycle and contradictionsResearch design; no admitted block
Repo-to-block pipelineSource shapes, stages, deterministic/human split, negative pathsMixes extraction, qualification and admission
SISOCRM ownership/data decisionsFirst-principles service-vs-own and data ownership reasoningOne product context
Teable absorption briefConcrete host-session/data/runtime seam questionsTeable-specific

Data and host platform

SourceContributionLimits
Reusable-block framework reportTyped domain port and Postgres adapter guidanceDesign recommendation, not production benchmark
Builder architectureControl plane, data adapter, policy, runtime and deployment decompositionInherited scoped-Postgres assumptions need testing
SISOCRM ownership/data decisionsOne server/separate schema and event-read-model rationaleDonor stack constrained the choice

Connectors and external actions

SourceContributionLimits
Connector summaryOpenConnector, Activepieces, Nango and Jentic comparisonProvider breadth does not equal uniform depth
OpenConnector spikeLocal generation, actions, encrypted credentials and OAuth receiptsStorage/tenancy unsuitable as inherited

UI, design and product shell

SourceContributionLimits
Design grammar and preference protocolCurrent join of validity gates, design axes, elicitation rounds, DesignDNA and focused experimentsExact axis levels, correlations and round policy remain unexecuted
Local corpus joinTwo complementary 21st stores and precise countsQuality and source readiness vary
Claude lane synthesisPreference learning, UI knobs and deterministic UI findingsConversation-derived synthesis
AutoSaaS UI requirementsRequired dashboard primitives and metadataEarly minimal registry
AutoSaaS methodFive-area shell and product-factory flowShell universality is unproven

Composition, verification and economics

SourceContributionLimits
Composition architecturePlan-then-fill, deterministic solver, model roles and hypothesesUnexecuted
Composition eval suite26 fixtures, 8 axes, 6 tiers and kill rulesRequires real capability contracts
Evaluation/admission planSeven gates, four fixtures and 20-task model matrixDesigned, not run
Decision ledgerRanked backlog, stop rules and hold/kill criteriaEarlier phase assumptions

Platform and competitor evidence

SourceContributionLimits
Platform deep dives67 initial builder surfaces plus expansion candidatesField depth varies
Platform depth triage117 ranked records and source-depth prioritiesAuthenticated behavior mostly unknown
Strict competitor censusComplete 118×144 structural denominatorFeature-specific direct evidence extremely sparse in strict snapshot
Phase 9 Wave 6–12 deep dossiersRepeated 10-surface evidence tranchesNot yet synthesized into one canonical current census

Evidence-accounting rule

The source inventory is exhaustive by file path for configured roots. This curated map is intentionally selective by meaning. A file being inventoried does not make every claim in it current; canonical synthesis must cite the direct receipt when exact counts matter.

Canonical source remains knowledge/03-EVIDENCE-MAP.md. This HTML is a generated projection; edit the source, then run generate-docs.mjs.