Skip to content

chore(docs): keep source synchronization traceable #237

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
yordis merged 1 commit into from
Oct 23, 2026
Merged

chore(docs): keep source synchronization traceable #237

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,6 +48,8 @@ Resource contracts and acceptance:
- [Responsibility acceptance criteria](reference/responsibility-acceptance.md)
- [Decision and Document contracts](reference/decision-and-document-contracts.md)
- [Decision and Document acceptance requirements](reference/decision-and-document-acceptance.md)
- [Source integration contracts](reference/source-integration-contracts.md)
- [Source integration acceptance requirements](reference/source-integration-acceptance.md)

## Explanation

Expand Down
9 changes: 9 additions & 0 deletions docs/explanation/architecture-resource-roadmap.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -112,6 +112,15 @@ Native manifest export already exists. Source integration still needs its own
mapping, provenance, reconciliation and export-fidelity contracts; it must
preserve the existing behavioral anchors and exact selections.

The proposed [source integration contract](../reference/source-integration-contracts.md)
defines a native-first boundary for immutable supplied bundles, explicit
identity and version mappings, provenance and guarded reconciliation. Its
[acceptance requirements](../reference/source-integration-acceptance.md) distinguish
same-store reapply from migration into a new store, where incarnation-bound
selectors require explicit rebinding. These are proposed contracts; source
records, reconciliation operations and executable acceptance are not implemented.
Remote connectors and additional format compilers remain separate milestones.

## Atlas Linter comes after the architecture resources

Atlas Linter is deferred until the remaining architecture resources and source
Expand Down
Loading
Loading