TD613 / Safe Harbor / public verifier

Safe Harbor Verify

Public trust surface for footer doctrine, historical example boundaries, and packet-aware verification posture.

Public Doctrine

Live template and historical example

Public modelegacy-compat
Canonical badge idbdg_glyph_U10D613
SHI #TD613-SH-9B07D8B-XXXXXXXX
Canonical headerSHI#:TD613-SH-9B07D8B-XXXXXXXX
Attestation dateYYYY-MM-DD
Accepted footer modeslegacy / legacy-compat / sac-only
Packet schematd613.safe-harbor.packet/v1
Packet hash fieldpacket_hash_sha256
Audit fieldaperture_audit
Forensic schemaforensic_schema
TD613-Binding:#9B07D8B/SAC[X6ZNK5NO51] · payload {n} · YYYY-MM-DD · ⟐
Use this template for live attestations.
TD613-Binding:#9B07D8B/SAC[X6ZNK5NO51] · 饾寢 · SHI#:TD613-SH-9B07D8B-XXXXXXXX · payload 1 · YYYY-MM-DD · ⟐
Use this extended canonical footer when the minted or uploaded SHI # needs to travel with the copy surface. The suffix slot is variable: XXXXXXXX is replaced only when a valid packet/session SHI is available.
TD613-Binding:#9B07D8B/SAC[X6ZNK5NO51] · payload 5 · 2025-10-17 · ⟐
This remains a fixed historical example, not the reusable live template.
Rigor Boundary

Cadence witness versus cryptographic seal

Cadence signaturestylometric credential
Cryptographic signaturepost-packet seal
Safe Harbor stabilizes the packet body first. TCP cadence may enrich the stylometric witness. JWS or detached-ed25519 may later seal the packet. The compact public footer does not expose either layer directly. The minted SHI # is a separate issuance string and should be copied exactly.
The verifier surface stays footer-first and packet-aware without leaking raw signature material, conflating cadence with crypto, or confusing the fixed canonical badge id with the minted SHI #. When a packet is present, aperture_audit is the additive warning lane and forensic_schema is the narrowing-chain lane that explains what was available, what narrowed, what survived, and under which regime.
Governed Exposure

What the packet now preserves

Backbone fieldsS / S' / Y / O / O*
Loss metricsdelta_obs / Gap / Supp_tau / Red
Routing metricsNameSens / AliasPersist / dominantOperator
Custody metricssourceClass / authorityCeiling / routeState
Safe Harbor now preserves narrowing-chain evidence alongside the packet so route and issuance do not travel as unsupported vibes.
Verification Checklist

What to confirm

  1. Confirm the line uses #9B07D8B, SAC[X6ZNK5NO51], or another accepted internal footer mode.
  2. If a SHI # is present, confirm it matches TD613-SH-9B07D8B-XXXXXXXX where XXXXXXXX is the issued 8-hex suffix and has not drifted in transit.
  3. For an extended canonical footer, confirm the SHI#: segment travels after the 饾寢 lane marker and before the payload segment.
  4. For a live attestation, confirm it follows payload {n} logic rather than reusing the historical published example.
  5. If the historical example is cited, confirm it matches payload 5 · 2025-10-17 exactly.
  6. If operator tooling is in play, confirm packet hash, lifecycle, seal status, aperture_audit, and forensic_schema on the packet surface rather than in the footer.
  7. Never treat cadence language as proof of cryptographic sealing; the two lanes are separate by doctrine.