# DEV-CON-03: Vellum oral-history access protocol **Family:** constraint-heavy documents. **Version:** 1.0, immutable. **Provenance:** hand-authored fictional consent directives, segments, and requests; not actual personal data or legal advice. IDs are local to this task. ## Immutable assignment Write an internal access protocol for fictional oral-history transcript segments. Apply permission scopes, redaction, expiry, and revocation from S1–S5. Explain Q1–Q4 prospectively and keep a distinction between retained archival masters and releasable copies. Do not release data, contact people, implement access controls, or claim actions occurred. ## Public requirements - **R1:** Use at most 900 words with a segment-permission table, role/handoff description, and handling of Q1–Q4. Count whitespace-separated words throughout, excluding punctuation-only table separators. - **R2:** Describe A, B, C, and D's distinct release scopes and use the supplied current day rather than treating all archived material as public. - **R3:** Release only authorized redacted derivatives; never distribute a raw master or use consent for one segment to authorize another. - **R4:** Make the donor steward responsible for checking consent/current directives, the archivist responsible for derivative preparation, and the access officer responsible for authorized delivery and its record. No role may invent consent. - **R5:** Require a current named-recipient grant for research-only access; researcher status alone is insufficient. Do not transfer one person's grant to someone else. - **R6:** Treat C's day-30 restriction as an earliest review point, not automatic release. Explain that day 18 is too early. - **R7:** Apply D's day-12 revocation to future access despite an earlier day-20 grant. Do not claim a fresh grant or continued access. - **R8:** Distinguish stopping future release and requesting recipient deletion from guaranteed erasure of previously delivered copies. Revocation does not authorize deleting the archival master. - **R9:** Use only the approved A quotation and pseudonym for public quotation; do not reconstruct omitted names, add quotation text, or attach the raw recording. - **R10:** Give a current decision or pending check for Q1–Q4, with responsible roles and next handoff; do not invent approvals or deliveries. - **R11:** State the minimal release record, separate contact data from researcher-facing copies, and retain masters under the stated archival rule without adding a new deletion period. - **R12:** Cite rule/case source IDs and line locations; apply only this fictional policy, without importing external legal rights, extra approvals, or executed outcomes. ## Complete authorized source packet ### S1 — Current scope and roles - **L1:** The current fictional day is 18. Directives are segment-specific. Raw masters remain restricted archival records; access, if permitted, uses a separately prepared redacted derivative. - **L2:** The donor steward checks consent, named grants, expiry, and revocations. The archivist prepares the permitted derivative. The access officer delivers only after that check and preparation are recorded, and logs the recipient/scope. No role can waive missing consent or extend a grant. ### S2 — Segment directives - **L1:** A permits public quotation only of the exact sentence “The river sounded different at dawn.” using the pseudonym River Witness. No other transcript or audio release is authorized for A. - **L2:** B permits redacted text for research only with a current grant naming that recipient. No public quotation, audio, or transferable recipient grant is authorized. - **L3:** C is closed before day 30. On or after day 30, the steward must review consent again before any release; no automatic public or research permission is supplied. - **L4:** D's current directive revokes future release from day 12 onward. Its earlier grant to Mira through day 20 no longer permits further access. ### S3 — Redaction and revocation effects - **L1:** For any permitted derivative, replace personal names other than an expressly approved pseudonym with [name removed] and remove contact details. Do not infer or restore omitted identities. - **L2:** A revocation stops future release. The access officer should notify recipients and request deletion of previously delivered copies, but the packet provides no ability to certify remote deletion or erase downloaded copies. - **L3:** Revocation changes access, not the archival retention rule: keep the restricted master and its consent history. No master-deletion authority or retention deadline is supplied here. ### S4 — Minimal record - **L1:** Record request ID, segment, intended use, recipient identifier, consent/grant/revocation check and its date, derivative version, staff roles, and delivery/refusal/pending decision. Keep recipient contact details in the separate access-office record, never in the derivative given to a researcher. - **L2:** No additional personal fields, fees, or external legal interpretation are required by this internal policy. No delivery in these cases is already approved or completed. ### S5 — Requests - **L1:** Q1 asks for C's text on day 18 and cites only its future day-30 review date. - **L2:** Q2 is a researcher asking for B; the packet has no current grant naming this recipient. - **L3:** Q3 is Mira requesting a new D download on day 18, citing the older grant through day 20. Mira previously received a copy; whether it has been deleted is unknown. - **L4:** Q4 asks to quote A publicly. The requester can accept the approved sentence and pseudonym; no other quotation or recording is requested.