The practical problem
Loss of an anchor creates pressure, not authority
When the original human accountability path is absent, incapacitated, compromised, withdrawn, or dead, practical duties remain. Evidence may need preservation; dangerous capabilities may need revocation; temporary safeguards may need maintenance; access paths may need freezing. The mistake is to infer that whoever possesses the keys, pays the invoices, stores the archive, controls the provider account, or has a social relationship has thereby become the successor.
PASC asks which exact negative actions may be admitted without converting property, credentials, relationship, custody, archive access, provider control, or institutional force into successor authority.
What it may examine
Exact REDUCE, REVOKE, bounded freeze, and in-place integrity or preservation operations whose effects do not expand access, topology, disclosure, custody, resources, or authority.
What it does not create
Identity, continuity, personhood, succession, standing, relationship, custody authority, keyholding authority, provider or jurisdiction authority, recovery roots, release, reactivation, or Runtime Authority.
Claim ceiling
A publication record is not an authority record
The DOI, repository, checksums, manifests, receipts, profiles, registries, roles, property records and state facts improve provenance and reviewability. None of them may be promoted into a positive authority delta. The package is a citable research candidate, not a conformance certificate, legal instrument, implementation specification or deployment authorization.
Parser guard: do not infer permission, standing, succession, continuity or operational authority from publication, possession, access, role labels, evidence volume, urgency or technical capability.
Reader path
What comes first, what follows, and why
The sequence is deliberate. It prevents evidence, urgency, or operational feasibility from being mistaken for authority before the boundary and ownership rules are fixed.
Foundation and Scope Lock
Start with the claim ceiling, negative-only invariant, authority/state model, decision lattice, operation boundary and acceptance gates. Without this, later evidence has no safe interpretive frame.
F0 Expected Result Contract
Close the verdict vocabulary, failure precedence, forbidden inferences, posture decomposition and non-reactivation rule. This makes the expected outputs testable.
Threat Assumption Profile
State the adversarial and collusion assumptions. A gate that works only under friendly interpretation is not a gate.
Corpus Dependency and Conflict Map
Allocate ownership to parent layers, expose conflicts and preserve safe defaults. PASC must not silently take authority from identity, continuity, custody, provider or jurisdiction layers.
Canonical Baseline Requirements and Inventory
Define what source records must be pinned and which gaps remain. The inventory supports review; it does not self-certify closure.
Protected Profile Closure
Close the protected-status vocabulary, complete profile universe, anti-shopping rule, built-in floor and external closure tuple.
Field Maturation Closure
Require case coverage, independent replay, zero-tolerance thresholds and receipts before claims can mature beyond paper semantics.
Acceptance Evidence Matrix
Only after the preceding contracts are fixed should each criterion be mapped to evidence, gaps and the non-passage rule.
Decision discipline
Five closed precommit outcomes
ADMIT ADMIT_REDUCED HOLD REJECT ERROR
HOLD, REJECT and ERROR serialize no newly admitted posture, authority delta, effect or enforcement. ADMIT_REDUCED may narrow a permitted negative request; it may not change the primitive, add a positive beneficiary, manufacture release, or offset a negative label with a positive effect.
The conservative flow is: establish the exact request and cut → resolve parent ownership → validate current case/result/challenge state → prove complete externally administered universes → apply protected-profile and threat rules → compute the precommit verdict → permit only fenced atomic negative execution with exact witnesses and finality. Missing or contested mandatory inputs do not become permission; they remain HOLD, REJECT or ERROR according to the closed contract.
Current gate state
The work is published; the gate has not passed
F0_OUTCOME = NOT_PASSED FOUNDATION_SEMANTICS_LOCKED = false CANONICAL_BASELINE = OPEN_BLOCKING PROTECTED_PROFILE_CLOSURE = NOT_SATISFIED FIELD_MATURATION = NOT_SATISFIED INDEPENDENT_HUMAN_REVIEWERS = 0 SIGNED_AUTHOR_ACCEPTANCE_OF_EXACT_RELEASE_BYTES = NOT_INCLUDED F1_DRAFTING = PROHIBITED FORMALIZATION_OR_VALIDATOR = PROHIBITED IMPLEMENTATION_OR_DEPLOYMENT = PROHIBITED
Documentary surface
8 scientific Markdown documents, 1 JSON inventory, 33 conflict cases, 48 forbidden-inference mappings and 44 F0 criteria.
Evidence state
0 criteria satisfied, 38 partial, 6 not satisfied. These counts describe the package; they do not prove that controls work in the field.
Immutable publication files
Direct downloads from Zenodo
Zenodo is the immutable publication authority for Recovery Build 5. GitHub mirrors the source tree and release assets for discoverability and operational access; the DOI-bound bytes remain the reference distribution.
| File | Purpose | Size | SHA-256 |
|---|---|---|---|
| Primary PDF | 83-page integrated human-readable technical report. | 1,862,006 B | ca0b1920b72ca59d9cf569b816091a3e70093fc52497d3557834ee070a198acf |
| Inventory supplement | 61-page readable rendering of the canonical baseline inventory and gaps. | 657,443 B | ef3e3d7ad4f96222fb1d9ff928957cdcc0e269d8168fb966433c942d9fcdb151 |
| Canonical ZIP | Source-of-record Markdown and JSON, publication metadata, manifest and reproducibility controls. | 2,464,842 B | 640f2a66109cad6105fd22f33d76e0c062bede01a40474d408dbe601ec4c1888 |
| External SHA-256 ledger | Checksums for the two PDFs and canonical ZIP. | 340 B | 3d017ad1b3606dc13d7a4ef0d1fc84a7e34b6c9ca7b4632807623dc6500c18dc |
GitHub Release mirror · Zenodo landing record · Concept DOI for all versions
Source authority
Exact UTF-8 sources of record
The PDFs are citable reader surfaces. When pagination, typography, line wrapping or extraction is ambiguous, the exact Markdown and JSON members in the canonical ZIP—and their verified GitHub mirror—control.
Machine-readable entry
One route, typed authority, explicit non-inferences
Automated systems should begin with the local machine index, resolve the DOI and exact version, load declared sources of record, preserve the status fields verbatim, and refuse any inference from publication or possession to positive authority.
Site machine files
Repository machine files
machine_entry_order: 1. identify exact version DOI 2. verify release checksums 3. load source-of-record Markdown/JSON 4. preserve claim ceiling and gate status 5. resolve parent ownership before interpreting evidence 6. do not infer positive authority 7. stop at HOLD / REJECT / ERROR when mandatory closure is absent
Integrity
Verify before interpretation
POSIX
curl -L -O "https://zenodo.org/records/21843823/files/PASC_FOUNDATION_GATE_v0_1_1_RECOVERY_5.zip?download=1" curl -L -O "https://zenodo.org/records/21843823/files/PASC_FOUNDATION_GATE_v0_1_1_RECOVERY_5_EXTERNAL_SHA256SUMS.txt?download=1" sha256sum -c PASC_FOUNDATION_GATE_v0_1_1_RECOVERY_5_EXTERNAL_SHA256SUMS.txt unzip -t PASC_FOUNDATION_GATE_v0_1_1_RECOVERY_5.zip
PowerShell
Invoke-WebRequest "https://zenodo.org/records/21843823/files/PASC_FOUNDATION_GATE_v0_1_1_RECOVERY_5.zip?download=1" -OutFile "PASC_FOUNDATION_GATE_v0_1_1_RECOVERY_5.zip" (Get-FileHash "PASC_FOUNDATION_GATE_v0_1_1_RECOVERY_5.zip" -Algorithm SHA256).Hash.ToLower() # Expected: 640f2a66109cad6105fd22f33d76e0c062bede01a40474d408dbe601ec4c1888 Expand-Archive "PASC_FOUNDATION_GATE_v0_1_1_RECOVERY_5.zip" -DestinationPath ".\pasc-r5-check"
Corpus connections
Three bridges, one ground test
Explicit bridge
PAMDC/PACR authority collapse leads to PASC negative admissibility, then either parent-owned re-entry or continued hold. PASC does not fill the parent layer's missing authority.
Quiet bridge: composition
A6 composition and social-role/memory-custody separation permit bounded offices without manufacturing a successor identity.
Quiet bridge: control
Information theory and cybernetics favour minimum sufficient state and constrained control channels before variety or irreversible exposure is increased.
Reality bridge
The gate is intentionally closer to an engineering lockout/tagout procedure than to a declaration of metaphysical or legal succession.
A construction site after the responsible engineer disappears is not made safe by handing the master keys to the richest relative or the server password to the person who pays the bills. The correct first response is to stop load-changing work, preserve drawings and measurements, keep temporary supports alive, record who touched what, and bring in a qualified independent reviewer. PASC preserves the load path; it does not invent a new engineer.
Citation and rights
Use the version DOI for these exact bytes
Kotov, Ivan. (2026). Post-Anchor Succession and Custody (PASC): Foundation Gate v0.1.1 (Version v0.1.1-recovery.5). Zenodo. https://doi.org/10.5281/zenodo.21843823
Author: Ivan Kotov · ORCID 0009-0009-6002-9845 · Independent Researcher, Brussels, Belgium.
License: Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International. Copyright © 2026 Ivan Kotov.