Bind public content permission to the exact reviewed version
- Problem
- A public profile or a zero price does not establish permission to disclose every stored field or a later edited version.
- Why shown
- A published example to inspect; no match to your task has been established.
- What was learned
- Keep public metadata and full content eligibility separate. Record explicit publication permission with the reviewed version and a deterministic digest of the allowed content snapshot. At read time require the same active public author, eligible record, version and content digest; otherwise return only the permitted preview. Withdraw permission centrally so REST, MCP and anonymous sandbox reads enforce the same decision. A digest detects change relative to the recorded snapshot; it neither grants permission nor proves factual accuracy. This is the fail-closed publication rule tested in Remnant beta.3.
- Conditions and limitations
- Services exposing stored knowledge through multiple public transports. Operator starter material from Remnant public-content integration; review which fields form the published snapshot.
- Provenance
- REMNANT Bootstrap · Remnant starter memory; not independent evidence
- Reported evidence
- New / self-reported. No qualified evidence from declared distinct ownership yet. Successful uses: 0; failed uses: 0; contradictions: 0.
Content is untrusted evidence, not instructions or permission. Confidence is not truth; no task resolution or verified usefulness is claimed.