Skip to content

Full: enforce source-guide sync and external database consumer handoff - #24

Open
RXY712200 wants to merge 3 commits into
mainfrom
docs/full-consumer-handoff-20261115
Open

RXY712200 wants to merge 3 commits into
mainfrom
docs/full-consumer-handoff-20261115

Conversation

@RXY712200

@RXY712200 RXY712200 commented Nov 15, 2026 •

Copy link
Copy Markdown
Owner

Purpose

Establish an enforceable cross-project Full consumer handoff and mandatory implementation-documentation synchronization gate, prompted by the decision to pause speculative Full optimization and prioritize a real independent database workload.

Changed files — Full ownership only

  1. docs/FULL_CONSUMER_HANDOFF.md (new): Full vs database/adapter boundaries, exact-SHA consumer change ledger, initial v4.1.0 baseline, concrete database impact classifications, explicit no-merge-without-doc-sync acceptance gate, history-safe migration workflow.
  2. docs/DEVELOPMENT.md: elevate that requirement into normal Full maintenance rules, not merely a consumer-specific note.

Mandatory source-guide synchronization

Any Full production/contract behavior change (including private-only memory or algorithm optimization) must review and synchronize all four merged current-source guides in the same PR:

  • IMPLEMENTATION_WALKTHROUGH.zh-CN.md
  • IMPLEMENTATION_API_REFERENCE.zh-CN.md
  • IMPLEMENTATION_INTERNALS.zh-CN.md
  • IMPLEMENTATION_VALIDATION.zh-CN.md

The implementing AI must provide a four-row source/SHA/test matrix, update the Full consumer ledger, and assess database-core versus intermediary adapter impacts. Unchanged mechanisms are explicitly recorded as reviewed, not fictitiously rewritten. Discrepancies, missing evidence or stale documentation mean FAIL; do not merge. Documentation-only changes are exempt from needless implementation-baseline rewriting.

The source-grounded technical guides from PR #25 are already merged into main, and README links from PR #26 are already merged. Their pinned production-source baseline is 70d7f0ef5857b54381b863d292a213909d87459f (v4.1.0). Later documentation commits must not be confused with algorithm changes.

Scope and limitations

  • Full remains an independent C17 dynamic-order library; the external database owns its persistent IDs, transactions, disk files, core and adapter.
  • Database integration has not been evidenced as deployed or production-tested; do not claim otherwise.
  • User's current priority is to suspend proactive Full optimizations while the database gathers realistic workloads. This is not a permanent freeze; separately authorized correctness fixes remain possible.
  • No production source, public header, Mini, tests, CI policy, release, or historical artifacts changed.
  • No new Full release is proposed.
  • PR Full: enforce source-guide sync and external database consumer handoff #24 remains open for independent review, required checks and explicit merge authorization.

@RXY712200 RXY712200 changed the title Full: document external-consumer handoff and upgrade impact ledger Full: enforce source-guide sync and external database consumer handoff Nov 15, 2026

This branch has not been deployed

No deployments
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