# Source Ledger and Rework Manifest

Status: current provenance and disposition ledger, 2026-09-30. This document owns source traceability, not conceptual definitions. The [index](../README.md) routes to authoritative owners. This reconciliation updates documentation traceability only; it does not change application, configuration, database, workflow or engine implementation.

## Disposition Rules

The original audit input contained 55 Markdown documents. The original rewrite below is a historical disposition record: four rewritten in place, four sources moved unchanged, 47 superseded/removed and 26 newly authored, yielding 28 active documents plus one reference and five archive documents. The subsequent [final-decision integration](#final-architecture-integration) edited existing documents only. Later implementation-contract and planning additions are part of the current workspace inventory. The 2026-09-23 reconciliation adds one justified cross-cutting authority document; the measured inventory on 2026-09-23 was 34 active Markdown documents, two reference documents and five archive documents, and the readiness register (2026-10-28) is the 35th (see the current-inventory correction below). It does not alter the archived source set or application scope.

### Current inventory correction

The historical 28-document count is retained above as provenance for the earlier rewrite. The filesystem inventory checked on 2026-09-23 was 34 active Markdown documents under `docs/`, excluding `docs/reference/` and `docs/archive/`; there were two reference documents and five archive files. The additional active documents reflect later contract/planning authoring as well as the new [core object model and authority](../architecture/core-object-model-and-authority.md). Future documentation checks must use the current inventory rather than the historical rewrite count.

**Active-document count, reconciled 2026-11-02.** The governed active set is **35**: the 34 above plus the [readiness register](../implementation/readiness-register.md), added on 2026-10-28 as the sole owner of temporary decisions, deferred capabilities, known defects, architectural gaps and production-readiness risks. The filesystem on 2026-11-02 holds 46 Markdown files outside `archive/` and `reference/`: the 35, four dependent implementation records added later without a count update (two Stage 3D handoffs, the data-defined semantics audit and the Products & Services proposal; none owns an architectural concept), and seven historical or stale documents outside the authority map (PRR-048). The two reference documents and the archive (four preserved source snapshots, their README and two build-record files) are not active owners. [Documentation governance](documentation.md#granularity-and-archive-policy) holds the governing statement. The classification of the four dependent records is recorded for project-owner confirmation; no document was added, removed or moved.

The current reference set also includes the subsequent nonnormative [object definitions discovery](../reference/object-definitions-discovery.md). It is a discovery record, not a canonical owner, implementation specification or addition to the active architecture-document count.

Removal means the former active document is no longer a source of implementation authority. It does not mean useful architecture was discarded. Active successors preserve compatible requirements and examples; [legacy reference](../reference/legacy-implementation.md) retains selected implementation context. Old marketing models, prescribed domain tables, APIs, customer migration claims and fixed module boundaries have no preservation obligation.

Historical paths below are identifiers, not broken links. Successor links point to current documents. The four original sources are preserved byte-for-byte in the [archive](../archive/README.md); their content is also redistributed below, not replaced by the archive alone.

## Original Architecture Sources

| Original path | Disposition and preserved source | Active successors |
|---|---|---|
| `new provisional docs/00-idiosyncrasy-combined-handoff.md` | MOVED unchanged to [00](../archive/architecture-sources/00-idiosyncrasy-combined-handoff.md) | All destinations for 01, 02 and 03 below; wrapper/version retained in archive. |
| `new provisional docs/01-idiosyncrasy-product-and-principles.md` | MOVED unchanged to [01](../archive/architecture-sources/01-idiosyncrasy-product-and-principles.md) | [Product](../product/definition.md), [capabilities](../product/capabilities.md), [objects/types](../architecture/objects-and-types.md), [retrieval](../architecture/retrieval.md), [evolution](../architecture/analytics-and-evolution.md). |
| `new provisional docs/02-idiosyncrasy-technical-architecture-and-data.md` | MOVED unchanged to [02](../archive/architecture-sources/02-idiosyncrasy-technical-architecture-and-data.md) | Canonical owners in [architecture map](../architecture/overview.md), including [composition](../product/definition.md#composition-and-extensibility). |
| `new provisional docs/03-idiosyncrasy-engines-workflows-and-mvp.md` | MOVED unchanged to [03](../archive/architecture-sources/03-idiosyncrasy-engines-workflows-and-mvp.md) | [Roadmap](../product/roadmap.md), [capabilities](../product/capabilities.md), [knowledge](../architecture/knowledge.md), [workflow](../architecture/workflows-and-automation.md), [evolution](../architecture/analytics-and-evolution.md). |

For each original: retain the snapshot; revise/merge/split its active content by the section mappings below; do not rename its basename or maintain another combined editable authority. Its archive status is provenance only, not a declaration that its architectural work is obsolete.

## Source Hashes and Combined Comparison

SHA256 before and after moving, verified 2026-09-11:

| Source | SHA256 |
|---|---|
| 00 | `C151B5FE00F8151C6AF22D65100A3113C5B168D4D9DA3387B5FC1EAE3D810C99` |
| 01 | `DE33949FDED6BC894A6C587DDC8465685F36B5DCB8CD9305384F5C4A5F460FE1` |
| 02 | `3025F4F3BF9F22FACC931BFD48216772651ACA9FD622CE745BC3DE1EAF398051` |
| 03 | `0E9379AA252DBA6BC70B05E55574381EA0FF1B667876C287BD1464DAEBF582B4` |

Each complete standalone source text occurs in 00. Removing those three texts from the comparison leaves only the combined title, provisional v0.4 label, handoff introduction and separators. No additional unique architectural section was found in 00. Its wrapper is preserved rather than treated as another current authority.

Source 01 repeats section number 3, and source 02 repeats 3.3. This ledger therefore identifies sections by title as well as number. Original numbering/version labels remain untouched.

## Source 01 Section Redistribution

| Source sections | Canonical content destination |
|---|---|
| Product definition | [Purpose and audience](../product/definition.md#purpose-and-audience) |
| Ease of use | [Ease of use](../product/definition.md#ease-of-use) |
| Not AI-dependent; AI-supported | [Product principle](../product/definition.md#ai-supported-not-ai-dependent); controlled implementation contract in [AI](../architecture/ai.md) |
| Self-optimising, suggesting and evolving | [Product principle](../product/definition.md#suggestion-led-evolution); operational [improvement loop](../architecture/analytics-and-evolution.md#improvement-loop) |
| Inherent growing knowledge | [Product principle](../product/definition.md#inherent-growing-knowledge); detailed [knowledge contract](../architecture/knowledge.md) |
| Structured retrieval principle | [Structured-first pipeline](../architecture/retrieval.md#structured-first-pipeline) |
| Holistic platform principle and capability list | [Capability catalogue](../product/capabilities.md#capability-catalogue), preserving breadth rather than a fixed module list |
| Universal data primitive and architectural rule | [Universal primitive](../architecture/objects-and-types.md#universal-primitive) |
| Platform versus modules: primitives, engines, capabilities, applications | [Composition and extensibility](../product/definition.md#composition-and-extensibility); list of semantic objects does not create multiple foundations |
| Extensibility and new capabilities | [Three levels](../product/definition.md#three-extensibility-levels) and [architectural test](../product/definition.md#seven-question-architectural-test) |
| Business identity, creation provenance and current administration | [Business model](../architecture/business-model.md#business-as-an-independent-entity), [identity and governance](../architecture/identity-and-governance.md#business-creation-and-administration) |
| Subscription entitlement and operational suspension | [Subscriptions and entitlements](../architecture/subscriptions-and-entitlements.md) |
| Competitive philosophy and long-term ambition | [Competitive position and ambition](../product/definition.md#competitive-position-and-long-term-ambition) |

## Source 02 Section Redistribution

| Source sections | Canonical content destination |
|---|---|
| Architectural objective | [Product purpose](../product/definition.md#purpose-and-audience), [runtime boundaries](../implementation/architecture.md); [overview](../architecture/overview.md#orientation) only routes |
| Core conceptual layers A-H | [Layer routes](../architecture/overview.md#conceptual-layer-routes), each deferring to its canonical owner |
| Universal primitive and examples | [Universal primitive](../architecture/objects-and-types.md#universal-primitive) |
| Type provides meaning | [First-class types](../architecture/objects-and-types.md#first-class-types) |
| Structured Retrieval First and Acme orders example | [Pipeline](../architecture/retrieval.md#structured-first-pipeline), [Acme example](../architecture/retrieval.md#acme-outstanding-orders-example), [indexes](../architecture/retrieval.md#indexes-and-consistency) |
| No special-case object model; Graph and DNA | [One connected model](../architecture/business-model.md#one-connected-business-model), [Business DNA](../architecture/business-model.md#business-dna) |
| Extensibility consequence | [Composition](../product/definition.md#composition-and-extensibility) |
| Scalar values remain valid; Addressable object principle | [Addressability and values](../architecture/objects-and-types.md#addressability-and-values) |
| Relationships | [Relationship identity](../architecture/business-model.md#relationship-identity-and-meaning), [integrity/lifecycle](../architecture/business-model.md#integrity-cardinality-and-lifecycle) |
| Knowledge Engine: content breadth and metadata | [Metadata and relationships](../architecture/knowledge.md#metadata-and-relationships) and its scope |
| Knowledge versus structured data, contact preference explanation and evolution | [Structured preference and explanation](../architecture/knowledge.md#structured-preference-and-explanation) |
| Knowledge provenance | [Provenance and authority](../architecture/knowledge.md#provenance-and-authority) |
| Events | [Event](../architecture/time-and-events.md#event) and [event responsibility](../architecture/time-and-events.md#event-responsibility) |
| Workflow model and full action list | [Definition/node contract](../architecture/workflows-and-automation.md#definition-and-node-contract), [action vocabulary](../architecture/workflows-and-automation.md#action-vocabulary) |
| Configuration | [Validity/representation](../architecture/objects-and-types.md#validation-and-configuration), [Business DNA](../architecture/business-model.md#business-dna), [execution](../architecture/workflows-and-automation.md#definition-and-node-contract) |
| Engine architecture and new engines | [Responsibility map](../architecture/overview.md#responsibility-map) defers to owners; [canonical engine definition and criteria](../product/definition.md#composition-and-extensibility) |
| Application generation and shared Customer example | [Applications as projections](../architecture/views-and-content.md#applications-as-projections), [shared representation](../architecture/business-model.md#one-connected-business-model) |
| AI architecture: controlled inputs, outputs, validation | [AI controlled access](../architecture/ai.md#controlled-access-and-retrieval), [every-output validation](../architecture/ai.md#validation-of-every-output) |
| Evolution engine and repeated post-sale tasks | [Evolution responsibility](../architecture/analytics-and-evolution.md#evolutionoptimisation-responsibility), [three-task example](../architecture/analytics-and-evolution.md#three-post-sale-tasks-example) |
| Architectural test | [Seven-question test](../product/definition.md#seven-question-architectural-test) |
| Identity, Business-scoped isolation, permissions and audit requirements throughout | [Governance](../architecture/identity-and-governance.md), [time/history](../architecture/time-and-events.md) |
| Rule/Policy/Constraint/Goal/Decision examples throughout | [Distinct semantic meanings](../architecture/semantics.md#distinct-conceptual-meanings); final governed composition supersedes the original incomplete precedence account |

## Source 03 Section Redistribution

| Source sections | Canonical content destination |
|---|---|
| Development strategy | [Foundation-first strategy](../product/roadmap.md#development-strategy) |
| Foundational data rule | [Object authority](../architecture/objects-and-types.md#universal-primitive), referenced by [foundation gates](../product/roadmap.md#foundation-gates) |
| Retrieval architecture requirement | [Retrieval authority](../architecture/retrieval.md#structured-first-pipeline), referenced by foundation gates |
| Initial engine priority: all four phases | [Broader capability priorities](../product/roadmap.md#broader-capability-priorities); preserved coverage defers to the final first-milestone implementation order |
| Initial business capabilities | [Representative scope](../product/roadmap.md#representative-business-scope), [catalogue](../product/capabilities.md#capability-catalogue) |
| Example cross-system workflow: twelve-step enquiry | [Website enquiry example](../product/capabilities.md#website-enquiry-example) |
| Knowledge workflow: pricing-policy PDF | [Seven-step knowledge case](../architecture/knowledge.md#pricing-policy-pdf-seven-step-case) |
| Self-optimisation workflow | [Improvement loop](../architecture/analytics-and-evolution.md#improvement-loop), preserving proposal, approval/rejection, measurement and business history |
| Future capability creation: equipment servicing | [Equipment-servicing example](../product/capabilities.md#equipment-servicing-example); no EquipmentServicingEngine required |
| Human-operated first: Marketing, CMS, Workflows | [Human-operated first](../product/roadmap.md#human-operated-first) |
| MVP success criteria: all eleven | [Eleven success criteria](../product/roadmap.md#eleven-mvp-success-criteria) |
| What not to build initially | [Explicit exclusions](../product/roadmap.md#explicit-initial-exclusions) |
| Long-term expansion model | [Long-term expansion](../product/roadmap.md#long-term-expansion-and-evidence-gates) |

## Other Input Documents

Every input below is REWRITTEN in place or SUPERSEDED/REMOVED; the table is the explicit deprecation notice for removed paths. Compatible details are consolidated, not independently authoritative at both old and new locations.

| Original path | Disposition | Destination and retained content |
|---|---|---|
| `AGENTS.md` | REWRITTEN | [Root routing](../../AGENTS.md); old product definition removed. |
| `docs/AGENTS.md` | REWRITTEN | [Docs instructions](../AGENTS.md), [governance](documentation.md), [development](../implementation/development.md), [security](../implementation/security-and-operations.md). |
| `docs/README.md` | REWRITTEN | [Index](../README.md); sole authority routes, not marketing-platform design authority. |
| `docs/architecture/overview.md` | REWRITTEN | [Navigation map](../architecture/overview.md); detailed taxonomy moved to product owner. |
| `docs/architecture/system-design.md` | SUPERSEDED/REMOVED | [Runtime](../implementation/architecture.md#layer-responsibilities); content-only platform flow superseded by shared capability composition. |
| `docs/architecture/job-queue.md` | SUPERSEDED/REMOVED | [Workflow scheduling](../architecture/workflows-and-automation.md#automation-and-scheduling), [async mechanisms](../implementation/architecture.md#async-work-and-extensions), [operations](../implementation/security-and-operations.md); old jobs schema not retained. |
| `docs/architecture/module-system.md` | SUPERSEDED/REMOVED | [Composition](../product/definition.md#composition-and-extensibility), [integration](../architecture/communication-and-integrations.md), [runtime packaging](../implementation/architecture.md#async-work-and-extensions); no isolated data universes or assumed loader. |
| `docs/architecture/cms-strategy.md` | SUPERSEDED/REMOVED | [CMS capability](../product/capabilities.md#websites-and-cms), [backend contract](../architecture/communication-and-integrations.md#normalized-backend-tool-contract), [WordPress](../implementation/wordpress.md), [Communication and integrations](../architecture/communication-and-integrations.md); old customer counts/permanent support/commercial promises not inherited. |
| `docs/architecture/UI Structure.md` | SUPERSEDED/REMOVED | [Brand/asset UI](../implementation/ui-system.md#brand-and-asset-editing), [views](../architecture/views-and-content.md), [knowledge](../architecture/knowledge.md); fixed marketing sitemap superseded. |
| `docs/database/schema.md` | SUPERSEDED/REMOVED | [Physical mapping](../implementation/architecture.md#physical-model-mapping); old domain relationships/JSON columns are not architecture. |
| `docs/database/tables/campaigns.md` | SUPERSEDED/REMOVED | [Marketing capability](../product/capabilities.md#marketing), [historical readiness](../reference/legacy-implementation.md#campaign-lists-and-readiness); incorrect campaign/automation field list discarded. |
| `docs/database/tables/content.md` | SUPERSEDED/REMOVED | [Content/variants](../architecture/views-and-content.md#content-and-variants); no inherited content schema. |
| `docs/database/tables/metrics.md` | SUPERSEDED/REMOVED | [Historical measurements](../architecture/analytics-and-evolution.md#measurement-and-historical-evidence); append-history requirement retained without prescribing metric tables. |
| `docs/development/coding-standards.md` | SUPERSEDED/REMOVED | [Engineering boundaries](../implementation/development.md#engineering-boundaries), [security](../implementation/security-and-operations.md). |
| `docs/development/patterns.md` | SUPERSEDED/REMOVED | [Development](../implementation/development.md), [runtime layers](../implementation/architecture.md#layer-responsibilities). |
| `docs/development/services.md` | SUPERSEDED/REMOVED | [Engineering boundaries](../implementation/development.md#engineering-boundaries); services need not equal engines. |
| `docs/development/repositories.md` | SUPERSEDED/REMOVED | [Runtime layers](../implementation/architecture.md#layer-responsibilities); parameterization/isolation preserved, not domain-specific repositories as foundations. |
| `docs/development/environment.md` | SUPERSEDED/REMOVED | [Configuration](../implementation/security-and-operations.md#current-configuration-contract), [encryption](../implementation/security-and-operations.md#external-secrets-and-encryption), [WordPress generation](../implementation/wordpress.md#generation-and-manual-editing); missing env-example reference corrected. |
| `docs/development/mysql-deployment.md` | SUPERSEDED/REMOVED | [Old setup boundary](../implementation/security-and-operations.md#old-schema-setup), [deployment](../implementation/security-and-operations.md#deployment-and-recovery), [Implementation architecture](../implementation/architecture.md). |
| `docs/modules/how-to-build-module.md` | SUPERSEDED/REMOVED | [Extensions](../implementation/architecture.md#async-work-and-extensions), [extending behavior](../implementation/development.md#extending-behavior); not executable instructions for absent runtime. |
| `docs/modules/channel-connectors.md` | SUPERSEDED/REMOVED | [Integration responsibility](../architecture/communication-and-integrations.md#integration-responsibility); useful operations not a frozen all-connectors API. |
| `docs/application/README.md` | SUPERSEDED/REMOVED | [Status](../implementation/status.md), [reference boundary](../reference/legacy-implementation.md#reference-boundary); old application not current architecture implementation. |
| `docs/application/dashboard.md` | SUPERSEDED/REMOVED | [Shell/dashboard reference](../reference/legacy-implementation.md#shell-and-dashboard), [layout reuse](../implementation/ui-system.md#layout-and-responsive-behavior). |
| `docs/application/brand.md` | SUPERSEDED/REMOVED | [Brand/asset editing](../implementation/ui-system.md#brand-and-asset-editing), [historical gaps](../reference/legacy-implementation.md#brand-and-assets), [Business DNA](../architecture/business-model.md#business-dna). |
| `docs/application/campaigns.md` | SUPERSEDED/REMOVED | [Marketing composition](../product/capabilities.md#marketing), [row interactions](../implementation/ui-system.md#actions-feedback-and-accessibility), [old readiness](../reference/legacy-implementation.md#campaign-lists-and-readiness). |
| `docs/application/automations.md` | SUPERSEDED/REMOVED | [Page builder](../implementation/ui-system.md#page-builder-pattern), [WordPress flow](../implementation/wordpress.md#observed-content-flow), [old inventory](../implementation/status.md#old-asset-inventory). |
| `docs/application/crm.md` | SUPERSEDED/REMOVED | [CRM capability](../product/capabilities.md#crm), [old placeholder](../reference/legacy-implementation.md#crm-analytics-and-native-cms). |
| `docs/application/analytics.md` | SUPERSEDED/REMOVED | [Analytics responsibility](../architecture/analytics-and-evolution.md#analytics-responsibility), [status](../implementation/status.md#new-platform-verification). |
| `docs/application/notifications.md` | SUPERSEDED/REMOVED | [Notifications versus events](../architecture/communication-and-integrations.md#notifications-are-not-events), [activity reference](../reference/legacy-implementation.md#activity-and-account-flows). |
| `docs/application/account-profile.md` | SUPERSEDED/REMOVED | [Auth/session safeguards](../implementation/security-and-operations.md#authentication-and-session-controls), [uploads](../implementation/security-and-operations.md#uploads-and-safe-rendering), [reference](../reference/legacy-implementation.md#activity-and-account-flows). |
| `docs/features/analytics.md` | SUPERSEDED/REMOVED | [Analytics](../architecture/analytics-and-evolution.md#analytics-responsibility); measurement/reporting/errors broadened beyond marketing. |
| `docs/features/automation.md` | SUPERSEDED/REMOVED | [Automation/scheduling](../architecture/workflows-and-automation.md#automation-and-scheduling); triggers/actions/loops/conflicts retained, old rules/executions tables removed. |
| `docs/features/campaign-management.md` | SUPERSEDED/REMOVED | [Marketing](../product/capabilities.md#marketing), [Goal](../architecture/semantics.md#goal); campaign requirements not a foundational schema. |
| `docs/features/channel-connectors.md` | SUPERSEDED/REMOVED | [Integration](../architecture/communication-and-integrations.md#integration-responsibility), [external failures](../architecture/communication-and-integrations.md#delivery-and-external-failures). |
| `docs/features/content-system.md` | SUPERSEDED/REMOVED | [Content/variants](../architecture/views-and-content.md#content-and-variants), [lifecycle](../architecture/views-and-content.md#lifecycle-and-collaboration); version/tag tables superseded. |
| `docs/features/media-management.md` | SUPERSEDED/REMOVED | [Media/asset responsibilities](../architecture/views-and-content.md#media-and-asset-management), [upload safety](../implementation/security-and-operations.md#uploads-and-safe-rendering). |
| `docs/features/notifications.md` | SUPERSEDED/REMOVED | [Communication](../architecture/communication-and-integrations.md#communication-responsibility); delivery channels/preferences/failure concerns retained. |
| `docs/features/publishing.md` | SUPERSEDED/REMOVED | [Delivery and failures](../architecture/communication-and-integrations.md#delivery-and-external-failures), [workflow execution](../architecture/workflows-and-automation.md#execution-and-evidence). |
| `docs/features/scheduling.md` | SUPERSEDED/REMOVED | [Scheduling](../architecture/workflows-and-automation.md#automation-and-scheduling); recurrence/timezone/DST/missed work and rate conflicts retained, FIFO/priority not universal guarantees. |
| `docs/features/user-collaboration.md` | SUPERSEDED/REMOVED | [Approval](../architecture/identity-and-governance.md#approval-and-delegation), [collaboration](../architecture/views-and-content.md#lifecycle-and-collaboration), [portals](../product/capabilities.md#customer-portals); agency-only framing superseded. |
| `docs/features/wordpress.md` | SUPERSEDED/REMOVED | [WordPress](../implementation/wordpress.md), [canonical tools](../architecture/communication-and-integrations.md#normalized-backend-tool-contract), [Communication and integrations](../architecture/communication-and-integrations.md); no automatic permanent-support commitment. |
| `docs/ui/overview.md` | SUPERSEDED/REMOVED | [UI system](../implementation/ui-system.md), [model projections](../architecture/views-and-content.md#applications-as-projections); backend-module-mirrored layout rule removed. |
| `docs/ui/layout.md` | SUPERSEDED/REMOVED | [Layout and responsiveness](../implementation/ui-system.md#layout-and-responsive-behavior). |
| `docs/ui/design-system.md` | SUPERSEDED/REMOVED | [Observed visual baseline](../implementation/ui-system.md#observed-visual-baseline); typography/sidebar/token discrepancy explicitly recorded, no unapproved wholesale redesign. |
| `docs/ui/consistency-rules.md` | SUPERSEDED/REMOVED | [Actions/feedback/accessibility](../implementation/ui-system.md#actions-feedback-and-accessibility); Marketing OS label removed from target instructions. |
| `docs/ui/components.md` | SUPERSEDED/REMOVED | [Reusable component contract](../implementation/ui-system.md#reusable-component-contract). |
| `docs/ui/brand-management.md` | SUPERSEDED/REMOVED | [Brand/asset editing](../implementation/ui-system.md#brand-and-asset-editing), [Business DNA](../architecture/business-model.md#business-dna). |
| `docs/ui/asset-library.md` | SUPERSEDED/REMOVED | [Brand/asset UI](../implementation/ui-system.md#brand-and-asset-editing), [content/media contract](../architecture/views-and-content.md#media-and-asset-management). |
| `docs/ui/analytics-ui.md` | SUPERSEDED/REMOVED | [Reporting patterns](../implementation/ui-system.md#shared-detail-and-reporting-patterns), [analytics](../architecture/analytics-and-evolution.md#analytics-responsibility). |
| `docs/ui/campaign-ui.md` | SUPERSEDED/REMOVED | [Shared detail patterns](../implementation/ui-system.md#shared-detail-and-reporting-patterns), [marketing capability](../product/capabilities.md#marketing). |
| `docs/ui/screens/campaign-detail.md` | SUPERSEDED/REMOVED | [Shared hub/states/accessibility](../implementation/ui-system.md#shared-detail-and-reporting-patterns), [marketing](../product/capabilities.md#marketing); no claim that an unwired campaign detail screen defines the platform. |

## Newly Authored Files

These 28 files are created by the rework and subsequent approved contract authoring, excluding the four unchanged archive moves and four in-place rewrites listed above. The final entry was added during the 2026-09-23 reconciliation.

| Created file | Role |
|---|---|
| [docs/governance/documentation.md](documentation.md) | Documentation authority and maintenance. |
| [docs/governance/decisions.md](decisions.md) | Originally an open-question register; now the settled final-decision evidence record. |
| [docs/governance/source-map.md](source-map.md) | This ledger and manifest. |
| [docs/product/definition.md](../product/definition.md) | Product and composition authority. |
| [docs/product/capabilities.md](../product/capabilities.md) | Capability catalogue and scenarios. |
| [docs/product/roadmap.md](../product/roadmap.md) | MVP and future scope. |
| [docs/architecture/objects-and-types.md](../architecture/objects-and-types.md) | Universal model and types. |
| [docs/architecture/core-object-model-and-authority.md](../architecture/core-object-model-and-authority.md) | Cross-cutting conceptual authority for object reality, definitions, derived State, history, workflows and explicit authority. Added 2026-09-23; detailed contracts remain with their existing owners. |
| [docs/architecture/business-model.md](../architecture/business-model.md) | Graph, relationships and DNA. |
| [docs/architecture/semantics.md](../architecture/semantics.md) | Distinct business semantics. |
| [docs/architecture/time-and-events.md](../architecture/time-and-events.md) | Temporal and event authority. |
| [docs/architecture/knowledge.md](../architecture/knowledge.md) | Institutional knowledge. |
| [docs/architecture/retrieval.md](../architecture/retrieval.md) | Platform-wide retrieval. |
| [docs/architecture/workflows-and-automation.md](../architecture/workflows-and-automation.md) | Executable configuration and timing. |
| [docs/architecture/identity-and-governance.md](../architecture/identity-and-governance.md) | Authority and isolation. |
| [docs/architecture/views-and-content.md](../architecture/views-and-content.md) | Model projections and content. |
| [docs/architecture/communication-and-integrations.md](../architecture/communication-and-integrations.md) | Communication and external boundaries. |
| [docs/architecture/analytics-and-evolution.md](../architecture/analytics-and-evolution.md) | Measurement and improvement. |
| [docs/architecture/ai.md](../architecture/ai.md) | Optional controlled intelligence. |
| [docs/implementation/architecture.md](../implementation/architecture.md) | Runtime guidance. |
| [docs/implementation/idy-007c-contract.md](../implementation/idy-007c-contract.md) | Frozen approved IDY-007C bounded workflow execution contract; section 13 of the implementation plan remains planning source material. |
| [docs/implementation/ui-system.md](../implementation/ui-system.md) | Reusable presentation and interactions. |
| [docs/implementation/security-and-operations.md](../implementation/security-and-operations.md) | Operational/security knowledge. |
| [docs/implementation/development.md](../implementation/development.md) | Build/contribution guidance. |
| [docs/implementation/status.md](../implementation/status.md) | Evidence and reuse dispositions. |
| [docs/implementation/wordpress.md](../implementation/wordpress.md) | Backend-specific knowledge. |
| [docs/reference/legacy-implementation.md](../reference/legacy-implementation.md) | Selective nonnormative context. |
| [docs/archive/README.md](../archive/README.md) | Archive status and navigation. |

### Subsequent Reference Record

| Created file | Role |
|---|---|
| [docs/reference/object-definitions-discovery.md](../reference/object-definitions-discovery.md) | Nonnormative discovery of reusable object definitions, Business configuration and the boundary between structure and platform behavior. |

## Preserved Decisions and Unresolved Detail

The four-source content is preserved in active text and examples, with exact snapshots providing a lossless backstop. The universal model, type definitions, Graph/DNA, scalar/addressability distinction, full retrieval dimensions, provenance/authority distinctions, action vocabulary, no-AI operation, governed proposal loop, business breadth and all eleven MVP criteria remain explicit.

The overview no longer defines composition terminology itself; that authority is in product definition. Fourteen engine responsibilities remain fourteen responsibilities, not fourteen software services or documents. Final execution guarantees now live in their canonical owners; the initial modular monolith implements them without requiring fourteen deployment units. Autonomy remains governed configuration, not invented tier privileges.

[D01-D10](decisions.md) are settled. The previous register's open-question statuses and conflicting topic labels are superseded by the final transcript and project-owner corrections. Implementation specifications and status remain separate; old code is not used to redefine semantics. Documentation maintenance is unnumbered governance, not final D10.

## Verification Record

Historical checks from the original rewrite on 2026-09-11, before final-decision integration. Counts and open-status findings describe that earlier snapshot, not the current architecture or checks rerun below:

| Check | Result |
|---|---|
| Input inventory against disposition ledger | PASS: all 55 original Markdown paths accounted for exactly once. |
| Actual changes against manifest | PASS: 26 created, four rewritten, four unchanged source moves, 47 superseded files removed. |
| Final documentation count | PASS: 28 active documents; 34 including reference and archive. |
| Relative file links and Markdown heading anchors | PASS: 948 checked, zero missing or retired targets. |
| Original architecture-source preservation | PASS: all four SHA256 hashes unchanged; combined-only wrapper identified. |
| Responsibility, terminology and scope counts | PASS: fourteen mapped responsibilities, nine workflow terms, eleven MVP success criteria. |
| Open-decision boundaries | PASS: ten decision entries explicitly OPEN with blocked-claim boundaries; D10 distinguishes approved structure from unassigned maintainers. |
| Markdown structure and diagnostics | PASS: balanced active code fences; no reported editor errors in checked documentation. |
| Architecture source review | No substantive source-content loss identified beyond intentional consolidation; original examples and unresolved choices remain traceable. |
| Non-documentation scope | PASS: all 79 pre-existing non-Markdown files hash-identical; no non-Markdown files created. |

The comparison includes application source, configuration and database files without exposing their contents. Only empty retired documentation directories were removed. No application tests, setup scripts, deployment, workflows or engines were run or implemented. These are documentation checks, not runtime/security certification or resolution of open architectural decisions.

## Final Architecture Integration

Integration date: 2026-09-11. Approver: project owner through explicit transcript answers and subsequent corrections/instructions in the documentation integration conversation. D01-D10 are confirmed complete. Original approval timestamps and omitted deliberation are not invented. The earlier source files and [ChatGPT D.txt](../../ChatGPT%20D.txt) remain unchanged; active canonical owners are the single current specification.

| Supplied evidence | Disposition and canonical owner |
|---|---|
| Transcript lines 1-82: D03.8 recap, D03.9 approval and ten Graph principles | [Business model](../architecture/business-model.md#assertions-derivation-and-applicability): semantics/direction, type constraints, temporal/contextual validity, no connectivity authority/inference, provenance-aware derivation, non-destructive conflicting Assertions and explicit scope. ClientCo/Service A/P123 example retained. |
| Lines 85-137: D05.29, explicit yes at 135 | [Action commit](../architecture/workflows-and-automation.md#action-preconditions-and-commit-boundary): all eight precondition categories, current authoritative version checks and stale waiting-project example. |
| Lines 140-175: D05.83, yes at 173 | [AI determination scope](../architecture/ai.md#materialised-validation-determinations): exact six scope/authority dimensions, no meaning expansion and Project:P123/Specification:v4/ProposalApproval example. |
| Lines 177-221: D05.84, yes at 219 | [AI determination lifecycle](../architecture/ai.md#materialised-validation-determinations), using [addressable historical transitions](../architecture/time-and-events.md#durable-history-and-transition-occurrences): independent Validation lifecycle, dependency re-evaluation, retained D88/D103 and prior Actions. |
| Lines 224-275: D07.24, yes at 273 | [Delegation](../architecture/identity-and-governance.md#approval-and-delegation): all seven arrangement fields, bounded authority, Policy/authentication controls, revocation and separate Stu/Manager/Worker-17 attribution. |
| D10.1, lines 288-307; yes at 416 | [Knowledge scope](../architecture/knowledge.md#scope-and-invariants): first-class capability from existing primitives, not a parallel knowledge universe. |
| D10.2, lines 308-329; yes at 417 | [Knowledge sources](../architecture/knowledge.md#sources-interpretation-and-context): document is a source, extraction/interpretation is not automatic truth or authority. |
| D10.3, lines 330-353; yes at 418 | [Knowledge context](../architecture/knowledge.md#sources-interpretation-and-context): Business/object/relationship/time/scope/applicability/provenance/standing/authority context. |
| D10.4, lines 354-377; yes at 419 | [AI assistance](../architecture/ai.md#responsibilities-and-output-forms), consumed by Knowledge: retrieval, summaries, extraction, contradictions, gaps and proposals remain governed interpretation. |
| D10.5, lines 378-389; yes at 420 | [Retrieval](../architecture/retrieval.md#request-and-result-contract): identity and authorised context before relevance/presentation; connectivity grants no access. |
| D10.6, lines 390-415; yes at 421 and closing approval | [Knowledge history](../architecture/knowledge.md#provenance-and-authority): retain 10/14 employee Assertions with source/time; current operative use is governed. |
| Project-owner correction: persistence and D07 | [Objects](../architecture/objects-and-types.md#storage-boundary), [history](../architecture/time-and-events.md#durable-history-and-transition-occurrences), [execution](../architecture/workflows-and-automation.md): durable authority; coherent state/history; optimistic versions; stale rejection; Unknown/Reconciliation; schema as implementation; projections non-authoritative. |
| Project-owner correction: D05/D07 retry | [Commands/Attempts/recovery](../architecture/workflows-and-automation.md#commands-executions-attempts-and-recovery): addressable execution, retained attempts, deterministic safe repetition, reconciliation for unsafe/unknown effects, duplicate Command identity. |
| Project-owner correction: D04 Policy | [Policy composition](../architecture/semantics.md#composition-and-conflict-resolution): explicit versions/relationships, governed composition/enforcement/exceptions, retained conflicts, defined deterministic or authorised human resolution, auditable result. |
| Project-owner correction: bootstrap, UI, distribution and demonstrator | [Genesis](../architecture/objects-and-types.md#controlled-genesis), [views](../architecture/views-and-content.md), [distribution contract](../architecture/workflows-and-automation.md#distribution-contract), [roadmap](../product/roadmap.md): modular monolith, early UI/login, optional Idiosyncrasy-first Business and full Spearmint lifecycle, not generic CRM. |
| Project-owner correction: Definition and Action foundation, plus explicit Option A clarification (2026-09-30) | [Definitions](../architecture/objects-and-types.md#generic-definition-payload-and-reference-contract), [publisher authority](../architecture/identity-and-governance.md#platform-definition-publication-authority), [external Action authority](../architecture/identity-and-governance.md#permission-scope-and-ownership), [Operation Contract](../architecture/operation-contract.md#actions-and-operation-contracts), [Communication](../architecture/communication-and-integrations.md), [Action execution](../architecture/workflows-and-automation.md), [implementation plan](../implementation/architecture.md#universal-definition-and-action-foundation-plan), [status](../implementation/status.md#generic-platform-definition-publication-boundary): Candidate A exact references; provider-independent Actions use existing Operation Contracts; external Actions authorize against the exact Operation Object identity through existing Business Grant/Policy Objects, not a Connection Type or parallel authority system; publisher configuration remains separate; the initial `send_email` Provider is simulation-only; no bootstrap, authority-management, live-provider or complete eight-Capability-Definition work is in scope. |
| Project-owner implementation instruction | [Mechanisms](../implementation/architecture.md), [14 priorities/milestone](../product/roadmap.md#implementation-priority), [invariant tests](../implementation/development.md#invariant-test-specification), [status](../implementation/status.md#first-milestone-evidence): smallest concrete implementation; semantics/mechanism/evidence kept separate; no additional architecture decision numbers. |
| Documentation reconciliation of Definition/Operation/External Action implementation (2026-09-30) | [Current implementation plan and boundaries](../implementation/architecture.md#universal-definition-and-action-foundation-plan), [Capability Definition/Application evidence](../implementation/status.md#capability-definition-and-application-build), [171-file public and 162-file internal package boundary](../implementation/status.md#target-release-foundation-evidence): current implementation status is distinguished from historical IDY-010 fixture evidence; no additional decision number. |

Bare references D05.28, D05.82, D07.23 and D09 closure, and references to earlier D05.21/D02.8, do not reproduce their complete clauses. The project owner explicitly confirms closure and supplies the applicable additional contracts; no absent wording or original title is fabricated. This is a traceability limitation, not grounds to reopen architecture. The enterprise-app-builder aside and conversational filler are nonarchitectural and omitted.

The previous register's labels are superseded, not renumbered into new decisions. Old topic links are routed to the actual canonical owner rather than used to mislabel final D04, D05 or D10. Original archive texts remain provenance, not competing current authority.

## Integration Verification

Checks performed for this integration on 2026-09-11:

| Check | Result |
|---|---|
| Source coverage review | Supplied Graph, Action commit, materialisation, delegation and all six Knowledge approvals mapped above; subsequent owner corrections and milestone instructions recorded separately. Missing original clauses remain an explicit provenance limitation, not reopened architecture. |
| Decision/status consistency | Ten entries D01-D10 marked SETTLED; no added architecture IDs. Targeted active-owner searches found no remaining OPEN architecture statuses or obsolete numbered-topic links. Business cases requiring human resolution remain distinct from architecture approval. |
| Relative links and Markdown anchors | PASS: 941 relative links across all 34 Markdown documents, zero missing files/fragments after repairs. Read-only PowerShell checks handled fenced examples, encoded spaces and duplicate-heading suffixes. |
| Structure and scope | PASS: 28 active documents, 34 total; 14 responsibility mappings, 14 implementation priorities and 11 broader MVP criteria. Balanced fences and no empty sibling sections. |
| File preservation | PASS against a 114-file pre-edit SHA256 baseline: 29 existing Markdown files changed, no files added/removed; all 80 non-Markdown files unchanged, including the supplied transcript and application/configuration/database files. All five archive files unchanged, including the four original architecture snapshots. |
| Implementation distinction | Settled contracts, chosen mechanisms and unbuilt evidence separated. First milestone and bounded Spearmint workflow specified; invariant test cases documented, not represented as existing or passing tests. |

Editor diagnostics were checked throughout the changed slices. At the time of this historical validation, no Git repository was available at the workspace root, so preservation used before/after hashes rather than a Git diff. This statement records that earlier validation environment and is not the current repository workflow. No credentials were printed or external effects invoked. This is documentation validation only: no runtime tests, dependency installation, setup, schema change, bootstrap, deployment, live integration or security certification was performed.

## Audit Correction Pass

On 2026-09-11 the project owner supplied the authoritative final titles for D01-D10 and explicitly authorised correction of all six findings from the subsequent read-only audit. D01-D10 remain SETTLED AND CLOSED. This pass clarifies the existing architecture; it creates no new decision number and no runtime implementation. Earlier verification rows above describe their original snapshots, not this correction's results.

| Approved correction | Canonical destination |
|---|---|
| Final D01-D10 titles and semantic routing | [Decision record](decisions.md): D08 is Configuration, Definition & Extensibility; D09 is Presentation, UI & Interaction Architecture; D10 remains Knowledge. Stable ID anchors retained. |
| Addressable State definitions, separate from labels and transition occurrences | [State identity](../architecture/objects-and-types.md#state-identity), with [history references](../architecture/time-and-events.md#durable-history-and-transition-occurrences) and minimal [physical specification](../implementation/architecture.md#physical-model-mapping) alignment. |
| Complete Workflow Step/Action/Action Execution/Attempt/Outcome/Effect/Event distinctions | [Workflow terminology](../architecture/workflows-and-automation.md#terminology); existing Command and scheduling terms retained. |
| Explicit non-destructive migration and re-entry | [Migration, re-entry and compensation](../architecture/workflows-and-automation.md#migration-re-entry-and-compensation): execution identity, definition bindings, prior visits and outcome evidence preserved. |
| Business extensibility cannot override foundational semantics | [Non-overridable foundations](../product/definition.md#non-overridable-foundations): authentication, authority, provenance, transition, Policy-enforcement and commit integrity remain runtime obligations. |
| UI/interaction state is not authoritative business State | [Interaction state and business State](../architecture/views-and-content.md#interaction-state-and-business-state): local interaction, persisted preference/draft and business mutation distinguished. |

The supplied titles are now known from the project-owner audit; earlier references to omitted original passages concern detailed source wording, not uncertainty about those titles or settled status. Implementation built/verified/deferred classifications are unchanged by these documentation corrections.

Focused verification for this correction pass on 2026-09-11:

- Exact-title comparison passed for all ten final headings; ten entries explicitly state SETTLED AND CLOSED. Existing `d01` through `d10` anchors remain valid; no additional decision entries were introduced.
- Cross-owner review and text assertions confirmed addressable State definitions versus primitive labels/transitions; the complete execution terminology; preserved identity, version bindings and history during migration/re-entry; the non-overridable foundations; and interaction state versus business State. These checks validate documentation, not runtime enforcement.
- Relative-link, heading-anchor and fenced-block checks passed: 964 links across 34 Markdown documents, with no missing targets or structural issues after anchor-spacing repair. Editor diagnostics reported no errors in all eight affected files.
- Before/after SHA256 comparison against 114 existing files found eight Markdown changes, no additions/deletions, no non-Markdown changes and no archive changes. The implementation-status document remains unchanged. No application code, schema, runtime test, bootstrap, installation or deployment was changed or run.

No remaining gap was identified within the six approved correction areas. Detailed original passages absent from the local transcript remain a provenance limitation, not missing approval or an open architecture decision.

## User, Commercial Model and Identity Reconciliation (2026-11-02)

Documentation-only reconciliation under explicit project-owner direction (Stu, 2026-11-02). It creates no decision number, adds no new owner document, and changes no code, database, Genesis, configuration or STAGING state. The four archive sources are unchanged.

| Project-owner direction | Canonical destination |
|---|---|
| User replaces Principal; Person is a Business-scoped profile; legacy Principal identifiers are implementation details | [Owner-correction note](decisions.md#unnumbered-cross-cutting-correction---user-replaces-principal), [identity and governance](../architecture/identity-and-governance.md), [legacy identifier map](../implementation/architecture.md#legacy-principal-identifiers), PRR-061 |
| Business-subscription-only commercial model, working billing bands, derived conditions, unsubscribed preview requirement, activation and lapse (intended future architecture; not implemented) | [Subscriptions and entitlements](../architecture/subscriptions-and-entitlements.md), [product definition](../product/definition.md#business-identity-authority-and-subscription), PRR-063, PRR-065, PRR-067 |
| Licensed and Guest Users; Licensed status never grants authority; Guest cannot execute Business operations | [Licensed and Guest Users](../architecture/identity-and-governance.md#licensed-and-guest-users), PRR-064 |
| Delegated authority for automation; proposed succession and pause behaviour (not settled) | [Delegated Authority For Automation](../architecture/identity-and-governance.md#delegated-authority-for-automation), PRR-062 |
| User account versus Business-scoped Person profile (intended conceptual model; mechanisms open) | [User Account And Person Profile](../architecture/identity-and-governance.md#user-account-and-person-profile), PRR-066 |

Frozen contracts and request documents carry a dated supersession note and are otherwise unchanged; dated historical records are not rewritten. No runtime test, build, migration or deployment was run.