Skip to content

feat: install document components and adopt versioned flows - #64

Merged
dapi merged 16 commits into
feat/141-source-format-bridgefrom
feat/141-document-components
Sep 7, 2026
Merged

feat: install document components and adopt versioned flows#64
dapi merged 16 commits into
feat/141-source-format-bridgefrom
feat/141-document-components

Conversation

@dapi

@dapi dapi commented Sep 7, 2026

Copy link
Copy Markdown
Owner

Component sources can now install DNA and base documents independently from optional flow contracts. Base creation leaves a document unadopted; explicit adoption binds its identity to a frozen bundle. Transitions and moves update the document, registry and lock atomically.

This adds schema-2 selection, four presets and adapters, versioned README/AGENTS composition, document commands, prepared-draft reference relocation, source/state validation, resolution plans and opt-in legacy migration with exact preview-digest consent. Failed rollback or cleanup retains a durable recovery journal, including the prepared input snapshot and ancestor permissions. Component mutations are supported on Linux/macOS.

Validation is green at caf0f3eaf3af290a702c8553795168584ac8b987:

Closes #62. Implements the CLI boundary of dapi/memory-bank#141; producer PR: dapi/memory-bank#143.

Stacked on #63. Release order: bridge, component-capable CLI, component payload. No release or live downstream migration is performed by this PR.

dapi added 15 commits September 7, 2026 02:19
…-document-components

* commit '8f91a5c514189a58a6a3597e947466bfbfc4ac73':
  fix: persist adapted ownership and pin original Git objects
  fix: drain CLI help when detecting the sync command
  fix: pin the canary to the canonical legacy template
  docs: scope the decision provenance reference
  docs: retain provenance with an acyclic evidence owner
  docs: remove the canary fixture dependency cycle
  fix: declare the downstream canary legacy source
…-document-components

* commit 'aae9a0f53b17ebc14920393aa03ea430eafdac8e':
  refactor: scope source envelope parsing to its schema
  refactor: avoid repeating source JSON validation
…-document-components

* commit '3b434fd93678c36447d10d4f308a39ce5d74b040':
  fix: keep legacy declaration capabilities fixed
  refactor: decode source declarations in one pass
@dapi
dapi marked this pull request as ready for review September 7, 2026 04:31
@dapi
dapi merged commit eedfdc5 into feat/141-source-format-bridge Sep 7, 2026
4 checks passed
@dapi
dapi deleted the feat/141-document-components branch September 7, 2026 08:55
dapi added a commit that referenced this pull request Sep 7, 2026
* feat: gate legacy sources before installation

* fix: declare the downstream canary legacy source

* docs: remove the canary fixture dependency cycle

* docs: retain provenance with an acyclic evidence owner

* docs: scope the decision provenance reference

* fix: pin the canary to the canonical legacy template

* fix: drain CLI help when detecting the sync command

* fix: persist adapted ownership and pin original Git objects

* refactor: avoid repeating source JSON validation

* refactor: scope source envelope parsing to its schema

* refactor: decode source declarations in one pass

* fix: keep legacy declaration capabilities fixed

* feat: install document components and adopt versioned flows (#64)

* docs: define component runtime execution plan

* refactor: avoid repeating source JSON validation

* docs: define durable component recovery execution

* feat: add component contract validation primitives

* fix: enforce frozen validation and projection boundaries

* fix: distinguish historical replay from transition authorization

* feat: compose component installations and explicit document transactions

* feat: complete component migration and explicit adoption runtime

* fix: reject unsupported URI schemes before relocation

* ci: fetch legacy ancestry for component migration fixtures

* fix: clarify template ownership with compatible renderer v3

* fix: preserve draft links and recognize source projections

* refactor: remove duplicate evidence sorting
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant