Loading record…

Loading records…

Proceed · hashedWatch · not startedpublic in the Ledger

Python library parsing shipping manifests into structured data for local dev environments

Sealed and hashed before the outcome was known. Nothing above this line can be edited, by you or by us.

rec-81e7e15d✓ check hashhashed Oct 5, 2026, 02:33 PM

PART A · THE DECISION

What was checked, and when

✓

Idea submitted

Oct 5, 2026, 02:33 PM

✓

Interpretation fork

Oct 5, 2026, 02:33 PM

✓

6 registries queried

Oct 5, 2026, 02:33 PM

✓

Verdict sealed · Proceed

Oct 5, 2026, 02:33 PM

append-only · nothing above can be rewritten

PART B · THE OBSERVATION

Measured against the committed line

Day 30

no data yet

○ pending

Day 90

scheduled · Day 90

○ pending

Day 180

scheduled · Day 180

○ pending

Day 365

scheduled · Day 365

○ pending

empty reads say "no data yet", never a zero

EVIDENCE AT SEAL

Frozen at 02:33 PM

IP India

Unreached · upstream error

Unreached

USPTO

no conflicting mark in USPTO class 9/42

Absent

GitHub

0 direct matches

Absent

PyPI

exact-name · not on PyPI under “unreached”

Absent

GitLab

0 exact project matches

Absent

npm

no exact or near name match on npm

Absent

5 of 6 reached · IP India unreached · gap disclosed

WHY THIS CANNOT CHANGE

Four reasons, all checkable

Hashed before the outcome

nobody knew if it would work

Absent ≠ Unreached

coverage gaps never look like empty registries

SHA-256 over Part A

anyone holding the JSON can recompute it

Frozen after the verdict

evidence and verdict are immutable on write

PART A · THE FORWARD FIELDS

Captured at seal because four of them cannot be recovered later.

collaborators

null · not captured on this pathnull

alternatives_at_commit

1 recorded · PyPI package extracting line-item coverageperishable

confidence_at_seal

inside the hash · not shown on the public surfacein the hash

abandonment_reason

null · run not abandonednull

founder_overrides

null · no gate was overriddennull

A perishable field not captured at seal is gone. No later migration can recover what was never asked for.

RECORD FORMAT

recordaurexis-part-a-v3

serialisationjq -S -c · trailing newline included

hashsha256 over record.json

storagecapability id · freeze after verdict

Verify it yourself

Sealed under an earlier format that predates the jq check. The hash is still checked on the verify page.

Open the verify page →

Download record.json

rec-81e7e15d · append-only · verifiable without Aurexis

Loading record…

← Records

Proceed · hashedWatch · not startedpublic in the Ledger

Python library parsing shipping manifests into structured data for local dev environments

Sealed and hashed before the outcome was known. Nothing above this line can be edited, by you or by us.

rec-81e7e15d✓ check hashhashed Oct 5, 2026, 02:33 PM

PART A · THE DECISION

What was checked, and when

✓

Idea submitted

Oct 5, 2026, 02:33 PM

✓

Interpretation fork

Oct 5, 2026, 02:33 PM

✓

6 registries queried

Oct 5, 2026, 02:33 PM

✓

Verdict sealed · Proceed

Oct 5, 2026, 02:33 PM

append-only · nothing above can be rewritten

PART B · THE OBSERVATION

Measured against the committed line

Day 30

no data yet

○ pending

Day 90

scheduled · Day 90

○ pending

Day 180

scheduled · Day 180

○ pending

Day 365

scheduled · Day 365

○ pending

empty reads say "no data yet", never a zero

EVIDENCE AT SEAL

Frozen at 02:33 PM

IP India

Unreached · upstream error

Unreached

USPTO

no conflicting mark in USPTO class 9/42

Absent

GitHub

0 direct matches

Absent

PyPI

exact-name · not on PyPI under “unreached”

Absent

GitLab

0 exact project matches

Absent

npm

no exact or near name match on npm

Absent

5 of 6 reached · IP India unreached · gap disclosed

WHY THIS CANNOT CHANGE

Four reasons, all checkable

Hashed before the outcome

nobody knew if it would work

Absent ≠ Unreached

coverage gaps never look like empty registries

SHA-256 over Part A

anyone holding the JSON can recompute it

Frozen after the verdict

evidence and verdict are immutable on write

PART A · THE FORWARD FIELDS

Captured at seal because four of them cannot be recovered later.

collaborators

null · not captured on this pathnull

alternatives_at_commit

1 recorded · PyPI package extracting line-item coverageperishable

confidence_at_seal

inside the hash · not shown on the public surfacein the hash

abandonment_reason

null · run not abandonednull

founder_overrides

null · no gate was overriddennull

A perishable field not captured at seal is gone. No later migration can recover what was never asked for.

RECORD FORMAT

recordaurexis-part-a-v3

serialisationjq -S -c · trailing newline included

hashsha256 over record.json

storagecapability id · freeze after verdict

Verify it yourself

Sealed under an earlier format that predates the jq check. The hash is still checked on the verify page.

Open the verify page →

Download record.json

rec-81e7e15d · append-only · verifiable without Aurexis