Data and state plane

Standardize typed data capabilities and ownership—not one database implementation inside every block.

Problem boundary

What this subsystem owns and what it must hand to the rest of Actionist.

What it owns

State classification and source of truth
Typed data ports
Schema and migration ownership
Events/read models/files/search
Data binding and rollback

What research already found

Postgres is a strong default for new owned transactional B2B data
Mature donor services should often retain native stores
One owner per table and migration is the strongest local rule
Cross-service views can use Actionist-owned event/read models

Open first-principles questions

What operations must v1 data ports support?
One DB, schemas, service stores or hybrid per client?
How are dual writes prevented?
What migration/rollback contract belongs in an assembled release?

Inputs

Product entities
Capability requirements
Existing client systems

Outputs

DataResourceContract
SchemaOwnerMap
Adapters
ReadModels

Connected knowledge nodes

P02 · Outcome and product specification P04 · Autonomous repo-to-block foundry P10 · Identity, settings and navigation host P12 · Deterministic composition planner P14 · Runtime, verification and release

Scientific research protocol

Every research owner uses the same evidence funnel. No padding is allowed when a denominator is inapplicable or evidence is unavailable.

Prior evidence auditRead the canonical spine, all domain-linked artifacts, the 17-industry catalogue and existing contradictions before searching again.

Commercial 100 → 10Define a denominator, map approximately 100 companies/products, and produce first-party dossiers for the strongest 10.

GitHub 100 → 10Search and dedupe approximately 100 relevant OSS projects, then deeply inspect the strongest 10 at the capability and architecture level.

Local estate joinInspect AutoSaaS, Great Library, SISOCRM, 21st stores and other domain-specific precedents already on the laptop.

Innovation 100 → 10Generate a wide divergent idea register, score it against the problem and retain the 10 strongest falsifiable innovations.

First-principles synthesisDecompose the irreducible problem, challenge inherited assumptions, reconcile contradictions and state the minimum sufficient design.

Contracts and experimentsReturn the proposed contract, dependency edges, unknowns, falsifiers, experiments, stop rules and decisions.

Independent verificationA separate verifier checks counts, links, source claims, overlap, contradictions and unsupported conclusions before promotion.

Evidence and agent outputs

Existing research remains source evidence. New agent packets are written to one owned workstream directory and linked here after verification.

Artifact	Location	State
SISOCRM ownership and data-layer decisions	`/Users/shaansisodia/SISO_Workspace/SISO_Agency/apps/SISOCRM/verticals/business-broker/OWNERSHIP-AND-DATA-LAYER-DECISIONS.md`	existing
Reusable-block framework report	`research/packs/source-files/reusable-block-framework-report.md`	existing
Block Contract data model	`research/actionmodel-builder-research-2026-08-26/phase-2/outputs/block-contract-v1.md`	existing
Future verified agent packet	`research/workstreams/P09-data-and-state-plane/runs/<run-id>/`	planned