Keep demo-safe proof summaries temporarily for founder review and investor walkthroughs.
Owner: Founder/Admin
A design-only register for evidence retention classes, access windows, expiry, legal holds, tombstones, revocation history, and lifecycle reporting before any retention database, purge job, archive worker, or deletion automation exists.
No retention runtime
Phase 184 defines retention behavior only. It creates no database table, purge job, archive worker, deletion job, legal hold automation, signed URL, export, download, or notification.
Retention lanes
8
demo to legal hold
Lifecycle states
10
draft to tombstone
Legal hold classes
6
incident to dispute
Runtime jobs
0
no purge or archive
Retention lanes
Owner: Founder/Admin
Owner: QA Lead
Owner: Security
Owner: Sponsor plus checker
Owner: Compliance
Owner: Finance and payment ops
Owner: Data Protection
Owner: Legal or founder-approved authority
Lifecycle states
Evidence metadata is planned or drafted but no storage object exists.
A reviewer or QA user requested proof capture under an approved scope.
Evidence summary cannot be shown until privacy checks and redaction rules are applied.
Only safe summary, caption, status, timestamp, and approved labels are viewable.
Evidence is part of an active review queue or correction loop.
Reviewer has closed the item with safe proof references and decision state.
The item can be considered by export policy but no export file exists.
The item is visible in a future scoped auditor view only if approved and redacted.
Expiry, purge, deletion, and external changes are frozen until hold release.
Future evidence is no longer accessible, but a non-sensitive audit marker remains.
Access windows
Every future external or sensitive report access must have approved start and expiry timestamps.
Access windows must record timezone and normalized UTC values to prevent expiry confusion.
Future auditor sessions should expire after inactivity; Phase 184 only designs the rule.
Extending a retention or access window requires independent checker approval.
Founder, security, or data protection can revoke future access with mandatory reason.
Legal hold freezes expiry until a release approval exists.
Legal holds
Scope: Contract, audit, buyer, supplier, or implementation dispute evidence summaries.
Release: Release only after dispute owner and checker approve closure.
Scope: Ledger, partner callback, reconciliation, COD, payable, receivable, or settlement evidence summaries.
Release: Release only after finance and payment ops close the exception.
Scope: Privacy drift, forbidden category, redaction failure, or personal data exposure evidence summaries.
Release: Release only after data protection approval.
Scope: Suspicious access, breached scope, credential exposure, provider risk, or incident quarantine summaries.
Release: Release only after security approval.
Scope: Future regulator observer or official review packets within formal scope.
Release: Release only after legal basis expires or formal closure is recorded.
Scope: Court, counsel, formal claim, or legal investigation readiness evidence summaries.
Release: Release only through legal authority and founder approval.
Tombstone rules
Tombstones keep safe metadata only, never raw screenshots, original files, transcripts, secrets, or signed URLs.
A future tombstone marker should not be editable without a correction audit trail.
Every expiry, deletion, revoke, or retention change needs a safe reason category.
If evidence is superseded, point only to an approved replacement reference, not raw storage paths.
Legal hold prevents tombstoning until the hold is formally released.
Access can expire while the non-sensitive audit history remains reportable.
Actor permissions
Can request
Cannot do
Can request
Cannot do
Can request
Cannot do
Can request
Cannot do
Can request
Cannot do
Can request
Cannot do
Lifecycle reporting
Shows counts by retention lane, lifecycle state, expiry bucket, and legal hold status.
Shows items nearing expiry, expired items needing tombstone decision, and renewal candidates.
Shows active holds by class, owner, scope, review date, and release requirements.
Shows future tombstone markers, reason category, replacement pointer, and non-sensitive audit trail.
Shows future auditor scopes, start/expiry, revoked status, and blocked attempts in aggregate.
Shows policy conflicts such as expired but legal-held, redaction pending but export requested, or scope breach.
Audit fields
Stable future retention register record id.
References Phase 183 auditor access design when applicable.
References Phase 182 export policy design when applicable.
Safe evidence reference, never raw storage object or signed URL.
Founder demo, QA, security, external auditor, export compliance, finance, data protection, or legal hold.
Draft, capture requested, redaction pending, redacted ready, review open, review closed, export ready, auditor scoped, legal hold, tombstoned.
Founder, QA, security, data protection, finance, legal, compliance, or sponsor.
Public-safe, internal, restricted, forbidden, legal-hold, or incident.
Contract, payment, privacy, security, regulatory, litigation, or null.
Future legal hold reference, not legal document payload.
Policy reference controlling retention duration.
Future access window policy reference.
Future retention expiry date unless legal hold overrides it.
Future retention review due date.
Future expiry timestamp.
Future tombstone timestamp.
Safe tombstone reason category.
Approved replacement reference if superseded.
Maker approval reference for sensitive retention actions.
Independent checker approval reference.
draft, active, expiring, expired, held, release_pending, tombstoned, rejected.
Future register creation timestamp.
Future register update timestamp.
Hard rules
Phase 184 is retention register design only.
Do not create retention databases, migrations, API routes, purge jobs, archive workers, deletion jobs, scheduler tasks, storage buckets, legal hold automation, notifications, emails, exports, signed URLs, downloads, or public links here.
Retention register design must never expose raw screenshots, original evidence files, provider URLs, signed URLs, storage keys, credentials, CNIC, OTP, PIN, bank details, customer transcripts, private notes, or payment references.
Tombstone is not deletion runtime. It is a future safe audit marker design.
Legal hold overrides expiry until formally released by authorized roles.
External auditors can view only approved redacted retention views later; they cannot extend access, release holds, create tombstones, or mutate evidence.
Every future retention action must be scoped, reasoned, maker-checker controlled where sensitive, and auditable.
Phase 184 does not delete, archive, purge, retain, or hold anything; it only designs how those controls may work later.
Retention register packet
{
"retentionRegisterDesignId": "evidence_audit_retention_register_design_184",
"phase": "Phase 184",
"route": "/business-pro/evidence-audit-retention-register-design",
"sourceAuditorAccessPolicy": "evidence_external_auditor_access_design_183",
"sourceGate": "FAEDA-EVIDENCE-EXTERNAL-AUDITOR-ACCESS-DESIGN-001",
"designOnly": true,
"createsRetentionDatabase": false,
"createsMigration": false,
"createsApi": false,
"createsPurgeJob": false,
"createsArchiveWorker": false,
"createsDeletionAutomation": false,
"createsLegalHoldAutomation": false,
"createsStorageObject": false,
"createsSignedUrl": false,
"createsDownload": false,
"createsExport": false,
"inheritedAuditorAccessFields": [
"auditorAccessRequestId",
"auditorType",
"auditorOrganizationRef",
"auditorIdentityRef",
"sponsorRole",
"legalBasisRef",
"scopeMatrixRef",
"redactionPolicyRef",
"allowedViewKeys",
"blockedViewKeys",
"makerApprovalRef",
"checkerApprovalRef",
"accessStartsAt",
"accessExpiresAt",
"revokedAt",
"revocationReason",
"lastViewedAt",
"blockedAttemptCount",
"status",
"createdAt",
"updatedAt"
],
"inheritedAuditorRevocationTriggers": [
"time_expired",
"scope_breach_attempt",
"contract_or_nda_end",
"identity_or_role_change",
"suspicious_download_pattern",
"privacy_incident",
"founder_or_security_revoke",
"legal_hold_change"
],
"inheritedAuditorScopedViews": [
"audit_home_summary",
"redacted_report_packet",
"closure_and_reopen_summary",
"redaction_status_view",
"retention_register_view",
"route_build_mobile_proof_summary",
"access_log_self_view"
],
"inheritedAuditorApprovalGates": [
"Auditor access request draft",
"Founder or authorized sponsor approval",
"Identity and organization verification",
"Legal basis and NDA confirmation",
"Scope matrix approval",
"Privacy and security redaction review",
"Maker approval",
"Checker approval",
"Time-boxed access instruction"
],
"inheritedRedactedEvidenceViews": [
"report header",
"metric summary",
"proof summary",
"decision trail",
"retention trail",
"access trail"
],
"retentionLanes": [
"founder_demo_snapshot",
"internal_qa_report",
"security_incident_report",
"external_auditor_packet",
"export_compliance_packet",
"finance_settlement_evidence",
"data_protection_register",
"legal_hold_register"
],
"lifecycleStates": [
"draft_registered",
"capture_requested",
"redaction_pending",
"redacted_summary_ready",
"review_open",
"review_closed",
"export_policy_ready",
"auditor_scoped",
"legal_hold",
"tombstoned"
],
"accessWindowPolicies": [
"fixed_start_and_expiry",
"timezone_normalized",
"inactivity_timeout",
"renewal_requires_checker",
"emergency_revoke_anytime",
"legal_hold_overrides_expiry"
],
"legalHoldClasses": [
"contract_dispute",
"payment_dispute",
"privacy_incident",
"security_incident",
"regulatory_request",
"litigation_hold"
],
"tombstoneRules": [
"no_raw_payload",
"immutable_marker",
"reason_category_required",
"replacement_pointer_safe",
"legal_hold_blocks_tombstone",
"audit_survives_access"
],
"actorPermissions": [
"Founder/Admin",
"Data Protection",
"Security",
"QA Lead",
"Finance/Payment Ops",
"External Auditor"
],
"reportViews": [
"retention_health",
"expiry_queue",
"legal_hold_board",
"tombstone_register",
"auditor_access_windows",
"retention_exception_watch"
],
"auditFields": [
"retentionRegisterId",
"sourceAuditorAccessPolicyId",
"sourceExportPolicyId",
"evidenceRef",
"retentionLane",
"lifecycleState",
"ownerRole",
"privacyClass",
"legalHoldClass",
"legalHoldRef",
"retentionPolicyRef",
"accessWindowRef",
"retainUntil",
"reviewDueAt",
"expiredAt",
"tombstonedAt",
"tombstoneReason",
"replacementEvidenceRef",
"makerApprovalRef",
"checkerApprovalRef",
"status",
"createdAt",
"updatedAt"
],
"hardRules": 8,
"nextAllowedGate": "phase_185_evidence_audit_exception_review_design"
}Next build gate
After retention is designed, the next safe move is an exception review gate for policy conflicts, expired-but-held records, missing approvals, and risky lifecycle transitions.