[bryansayler]

Outcome

Adds a scoped candidate context profile and contributor entry points; preserves local source ownership and applicable behavior differences.

Keep Quirk's creative, capability, and participatory breadth while preserving exact originals, untried opportunities, quiet participation, useful divergence, scoped preferences, and honest evidence. Children inherit the owning profile unless a meaningful local difference exists.

Exact subject

• Base SHA: eb889adf3009951de873890103199600f4aad20f
• Head SHA: 2710ebe9169ea1226b0e767d3bb41c9ec69d2c35
• Tested subject SHA: 16d4219de7f80c18a8daf3a1082af5ab29a4247b
• Changed paths: .quirk/context-profile.json, QUIRK-CONTEXT.md, README.md, AGENTS.md, CLAUDE.md, templates/README.md, tests/test_agent_assets.py

Scope and authority

Candidate IMPLEMENTATION_DETAIL. No merge, canon/admission, release, production execution, deployment, or external publication authority is granted by these files. Existing owner review and merge rules remain in force.

Semantic impact

Domain extension and projections of existing source/context/receipt boundaries. QC01–QC12 are candidate requirement labels, not new canonical registry concepts. No registry definitions or frozen Core contracts changed. A context source and a candidate profile cannot admit themselves.

Evidence and verification

scripts/validate.sh passed on the exact subject in a normal checkout: 233 unit tests plus executed validators/lint. Ruff and actionlint were unavailable and reported skipped. A worktree run did not apply existing scoped lint exemptions; those warnings were not changed or suppressed by this PR.

Receipt: .quirk/evidence/context-continuity-16d4219de7f8.json at 2710ebe9169ea1226b0e767d3bb41c9ec69d2c35; receipt digest sha256:66e6d35578c37906b8792d17ec7609994f0adbe80ccd6077eb387147b31f558d. Subject commit: 16d4219de7f80c18a8daf3a1082af5ab29a4247b.

Checks not established: receiving-host loading, universal synchronization, participant benefit, production performance, or deployment. Delivered files remain distinct from loaded context and observed behavior.

Interoperability impact

The profile references the candidate Core contract by exact content digest. It does not replace Common Records or authorize a new shared service. Existing consumers can ignore the additive profile until deliberately integrated. Private material stays within its source audience.

Risk, rollback, and residue

The principal risk is treating written guidance as runtime compliance. Profile evidence states therefore do not self-attest adoption. Revert the scoped candidate files/changes independently; preserve creative originals, prior decisions, and active withdrawals. Closed/offline hosts and event subscriptions remain unintegrated.

Final receipt binding

The local evidence-receipt validator passed at the listed final head with --require-covered-diff: 83 receipts validated, including historical receipts. The range is the exact base-to-head pair above. This is a local verification result; it does not assert hosted CI completion or owner approval.