POM-RX v0.1 security boundaries
A guide to structural limits, unresolved areas, and responsible reporting.
POM-RX v0.1 — public working specification and tested prototype.
Pinned public commit 6f421c540e9a47a971840847547c9bfc951e1d46
Structural inconsistencies
What the reference verifier can reject in supplied receipts.
These rejections concern the form and internal links of a chain. They do not prove that an action, source, or external fact is safe.
Missing preflight or incompatible order
A supplied chain must start with preflight and retain a compatible phase order.
Method or policy divergence
Supplied `method_hash` and `policy_hash` values are among the fields compared in a chain.
Broken hash link
Each later receipt must be hash-linked to the preceding supplied receipt.
Invalid identifiers or phases
Supplied identifiers, phases, and outcomes must meet the expected structure.
Unexpected structure or fields
The verifier can reject supplied structure that does not match its expected keys.
Incompatible outcomes
Declared outcomes must remain compatible with their corresponding phase in the supplied chain.
Unresolved boundaries
What POM-RX v0.1 does not establish.
These limits remain explicit even when a supplied chain passes structural checks.
Compromised or dishonest source
A structural check cannot establish that a source was honest before supplying a receipt.
Truthful external acknowledgement
An assertion or acknowledgement from outside the chain may remain false or incomplete.
Keys and private data
Protection of source keys and private data is not established by a receipt chain.
Chronology and independent observation
The chain provides neither trusted chronology nor independent observation nor execution blocking.
Responsible disclosure
Report a problem without publishing sensitive data.
The pinned security policy asks that a suspected sensitive vulnerability is not opened as a public issue.
Include in a report
The affected component and commit, expected and observed behaviour, reproduction steps, potential impact, and a suggested mitigation when available.
Do not include
Credentials, seeds, personal data, or third-party secrets.
Send a responsible report to contact@swisstokint.ch
Security boundary
A public prototype without an independent audit or guarantee.
The pinned security policy describes an experimental open-source prototype that has not completed an independent security audit. This page explains limits; it is not a security control.
The pinned public commit contains the `pom-rx/0.1` schema, one Node/TypeScript reference verifier and one seven-test Node suite. The verifier checks the supplied structure, contiguous phase order, selected shared fields and receipt hash links.
These checks apply only to the supplied receipts. They do not establish trusted chronology, the truth of an external fact, source authenticity, authorization consumption, independent observation or execution blocking. POM-RX v0.1 does not place orders or custody assets, and is not a production control, audit, certification, or security or performance guarantee.
Pinned public sources
Read the exact sources before inferring a capability.
Every link leads to the same immutable public commit, without relying on `main` or a later version.