Standards and regulatory position

Where the standard gets written.

Certisyn writes standards, files them, and publishes the tests that let anyone check whether an implementation, including its own, conforms.

Everything on this page is on a public record you can open yourself. Items marked Submitted keep that label until the body publishes the outcome.

The position

A framework can name what must be governed without providing any instrument by which a third party can test whether it was.

The ACSC Essential Eight is a national security baseline with no standards body behind it, so maturity is self-asserted. A negative forensic finding is stated as a claim about the universe when what was established is a claim about a bounded set. An agentic AI operator asserts control claims that no counterparty can falsify.

In each case the gap is the same and it is not technological. There is no form in which the claim can be stated so that it becomes checkable. Certisyn writes that form, files it with the body that owns the area, and ships the test alongside it.

Core proposition
A standard that cannot be tested is an opinion with a document number. The contribution Certisyn makes to any body it joins is not the text. It is the test that comes with it.
Status

Every specification is an individual submission to the IETF.

Each specification below is filed with the IETF as an individual submission. Intended status is declared by the author. A monitoring process runs daily and keeps the status of every specification aligned to the public record.

Bodies Certisyn has applied to are listed as Submitted, in their own table, and move to the record when the body publishes the outcome. Only public-record items are listed.

The instruments

Each specification exists because a claim was being made in a context where nobody could test it.

Attestation Reconciliation Protocol
Intended status: Standards Track · SCITT area · Individual submission

Establishes whether an accountable principal stands behind an autonomous agent, reconciled against sovereign registers with minimum disclosure. Section 6.4 binds every read of the settlement ledger to a request and answers it with a signed response carrying the sequence number and head digest it was served against. A not-entitled read and a not-found read return the same response, so no endpoint becomes an existence oracle.

AI Governance Verified
Informational · Individual submission

Agentic AI governance made checkable rather than asserted: the control claims an operator makes about an agent, and the cryptographic evidence that must exist before a third party can accept them. Written against the EU AI Act general-purpose obligations and ISO/IEC 42001, which specify what must be governed but not what a third party may verify.

Essential Eight Verified
Informational · Individual submission

A verification standard for the ACSC Essential Eight Maturity Model. The Essential Eight is a national security baseline with no standards body behind it; maturity is self-asserted and, today, unfalsifiable. The same construction applies to any sovereign framework that names requirements without providing an instrument to test them.

Coverage Attestation Profile
Informational · Individual submission · Posted 20 August 2026

Makes a negative finding falsifiable. “This message is not present” is a claim about the universe; what was established is a claim about a bounded artefact set examined to a stated depth. Rule 6 refuses an absence claim that does not carry the population it is an absence from. Rule 7 refuses a clean verdict from a run that failed, exhausted, or became unavailable partway. Rule 1 refuses any remainder that reconciles only by arithmetic. None of it requires the generative step to be deterministic, which is what makes it usable where AI sits in the workflow.

Conformance Continuity
Informational · Individual submission

A conformance claim names a subject, a baseline and a period, and all three move. Baselines are superseded, jurisdictions recognise each other's baselines in incompatible vocabulary, and an environment running non-person entities changes composition faster than any attestation period. The Continuity Binding carries a verified claim across one of those boundaries while naming what carried, attributing the equivalence judgement to a party under a declared basis, holding carried evidence to the provenance class it was collected at, and enumerating every target outcome that did not carry. A claim presented as successor conformance without the binding is detectable by inspection.

Chorale Protocol
Experimental · Individual submission

Interception-resistant packet transmission for settings that already accept a co-presence setup cost. Its load-bearing section is not the transport but the admission control: three confidentiality regimes, the keying conditions under which each may be relied upon, and a per-message comparison of the regime a policy requires against the regime the session can achieve. A raised regime is relied upon only when independently corroborated, an uncorroborated claim down-rates rather than inflates, and the send refuses rather than proceeding below the floor. A specification that declines to attest the rung its construction has not earned.

Every filed draft resolves at datatracker.ietf.org under its draft name. Source and conformance classes are published at github.com/Certisyn-Inc/certisyn-drafts.

On the public record

Where Certisyn sits on the public record.

Author means normative text or research filed under Certisyn's name. Filed means a comment or submission entered on a public docket. Member means an accepted membership, listed in the body's own directory where the body publishes one. Integrated means a Certisyn determination endpoint wired into the named system and announced by its operator. Submitted means a contribution or application sent to a body and awaiting its decision or publication. Presented means a talk given at a published programme.

BodyRoleWhat is on the record
IETF Author Internet-Drafts filed and live on the Datatracker, one of them with intended status Standards Track in the SCITT area. All are individual submissions. Beyond authoring: a Last Call review submitted on draft-ietf-scitt-receipts-ccf-profile-04, in the public working group archive.
Zenodo Author Joint Interoperability Report: Independent Runs, Findings and Disagreements Recorded by SCITT Working Group Participants, version 1.1, published 12 October 2026. Joel Hillier is 1 of 18 listed authors, for Certisyn, Inc. DOI 10.5281/zenodo.23333369.
FCC Filed Participated in both rounds of the Next Generation 911 rulemaking. Comments (filing 2026080977595899) filed 9 August 2026 and Reply Comments (filing 202608260288428615) filed 26 August 2026, in PS Docket 21-479 (Facilitating Implementation of Next Generation 911 Services) and PS Docket 13-75 (Improving 911 Reliability), against Commission document FCC 26-39. Both are retrievable from the Commission's Electronic Comment Filing System.
US Treasury Filed Comment on the proposed GENIUS Act rule on payment stablecoin issuance, offer and sale (91 FR 53368, RIN 1505-AC95), Docket TREAS-DO-2026-0496. Submitted 10 October 2026 and posted 14 October 2026 as comment TREAS-DO-2026-0496-0072. Proposes a Reasonable Belief Record as the evidence for the reasonable-belief and controls conditions.
US Securities and Exchange Commission Filed Comment on Regulation Crypto Assets (91 FR 54510), File No. S7-2026-27, received 17 October 2026 and listed on the Commission's comment file as Dr. Joel Hillier, Founder and CEO, Certisyn, Inc.
Federal Reserve Board Filed Comment on the proposal Implementing the Federal Reserve Board's Responsibilities under the GENIUS Act (R-1899), posted 15 October 2026 as comment FR-2026-0033-01-C18. Addresses the reserve-side denominator through a Reserve Coverage Record.
NAESB Filed Public comment, 21 August 2026, on revised product cybersecurity procurement contract language for critical infrastructure, acknowledged by NAESB staff on 21 August 2026 and posted on the NAESB site for the comment period.
DFRWS USA 2026 Presented Presented at the Digital Forensic Research Workshop, George Mason University. Five substantive contributions followed to speakers within the fortnight, each answering a specific open question put to the room rather than restating a capability.
Hashgraph Online Member Partner programme member, participating in the Registries Subcommittee. HOL is part of the Hiero Project under Linux Foundation Decentralized Trust. Certisyn has volunteered to run a conformance-and-vectors workstream so that every standard ships with a runnable class, negative controls and declared coverage gaps.
DAIAA Member Member of the Decentralized AI Agent Alliance, active in the Agent Privacy and Security subgroup.
OpenID Foundation Member Member of the OpenID Foundation, confirmed by the Foundation on request. Comment submitted on OpenID Connect Key Binding 1.0 draft 03, arguing that proof of possession is required and that its mechanism sits outside the specification.
Internet Court Integrated Certisyn determination endpoints integrated with Internet Court, the adjudication layer for agentic commerce built on GenLayer, announced on 19 October 2026 in a post by Internet Court co-founder Burak Rahil, and acknowledged by Certisyn. Certisyn verifies the claim before funds move. Internet Court adjudicates where the claim does not hold. Determinations are attested by GenLayer validators that Certisyn does not operate, pay or select.

Submitted

Contributions and applications sent to a body and awaiting its decision or publication. Each moves to the table above when the body publishes the outcome.

BodyRoleWhat has been sent
Proof-of-Control Initiative Submitted Application for Founding Contributor status as an independent verifier, with a per-subject conflict-of-interest gate and a standing offer of offline verifiers and crosswalks. Written comments on the assessor and independence provisions are open on the public record as issues 130, 131, 132 and 133, filed 17 October 2026, with a crosswalk contribution for IETF SCITT and RATS in pull request 137. The public comment window closes 30 October 2026. Standard at github.com/LFDT-ProofOfControl/ov-poc-standard.
NIST Digital Forensics Artifact Catalog Submitted 1,848 candidate entries submitted on 17 August 2026 to the catalog team, each with its own provenance, with the CAP-1 coverage attestation profile alongside. Catalog at artcat.nist.gov.
SWGDE Submitted Modification request to the SWGDE Secretary on 29 August 2026 for 2 published documents (18-Q-001 and 12-Q-001), with a contributed technical note on the benchmark corpora used to validate digital image manipulation detection. Documents listed at swgde.org.
IAB post-quantum workshop Submitted Position paper to the programme committee, 26 August 2026: Four Vocabularies for What a Verifier Could Not Determine, and the gap post-quantum migration falls into.
The discipline

Five rules govern everything above.

1
Every normative claim ships with a test
Each specification is published with an executable conformance class. One command, no network access, nothing to install. Coverage gaps are declared in the run record before anyone runs it rather than discovered afterwards.
2
The document is checked against the issuing authority, not against itself
Certisyn's filing register asks the IETF which revisions are actually posted, fails on any the register omits, fetches each filed text from the authority's own archive and fails unless the local copy is byte-identical. It exits non-zero when the authority is unreachable, on the principle that an unreachable authority is not a pass. Its first run found two posted revisions nobody had recorded.
3
Independent reproduction is invited, not tolerated
Two external reviewers executed the conformance class on their own machines, on macOS and on Linux, and reproduced the deterministic rows. Both then attacked the evidence rather than the protocol. Their findings are closed and now carried as standing rules, so the same class of gap cannot reappear.
4
The instrument is pointed at its author first
The Coverage Attestation Profile was run against Certisyn's own engine before it was offered to anyone. It refused: 227 catalogued check identifiers, 6 examined, 221 unaccounted. The engine was changed, not the specification.
5
Filed is tracked separately from adopted
A daily monitoring agent keeps every specification's status aligned to the public record. A specification that has been filed is shown as filed. A specification no body has taken up is shown as founder-held.
Governing logic
Certisyn seals what can be verified and refuses to seal what cannot. A company that will not round its own numbers up is the one an institution can trust with someone else's.

One consequence worth stating. A cross-check during this work surfaced an interoperability trap reaching well past any single document: a widely used CBOR library, in its canonical mode, applies a different map-ordering rule than the RFC the specification pins. An implementation that imports it ships non-conforming bytes and receives no error saying so. Findings of that kind surface only when a specification is testable and someone has been invited to attack it.

What Certisyn brings to a body

Three things, in the order they are usually needed.

Normative text that carries its own test

A working group can adopt a specification and discover eighteen months later that two conforming implementations do not interoperate. A conformance class shipped with the text moves that discovery to the week of publication. Certisyn has volunteered to run exactly this workstream inside the Hashgraph Online registries programme.

A vocabulary for what could not be determined

Most verification vocabularies have a word for pass and a word for fail and nothing precise for the third case. Certisyn's work across the Coverage Attestation Profile and the reconciliation protocol is the same argument in different settings: indeterminacy has to be expressible, or it gets reported as one of the other two.

An implementation that already runs

Every specification listed here is implemented in a platform operating in production, certified to ISO/IEC 27001:2022 and ISO 9001:2015. Text and running code are filed together because a body evaluating a proposal should not have to take the author's word for whether it can be built.

Where to check

Every claim on this page resolves somewhere we do not control.

This is the whole list. If a statement about Certisyn cannot be checked from one of these, treat it as unverified until it can.

Filed specifications

datatracker.ietf.org — each draft by name, with revision history and posting dates.

IETF IPR disclosures — Certisyn's licensing statements on the drafts, published by the IETF, for example the General License Statement for the Coverage Attestation Profile.

Source and conformance classes

github.com/Certisyn-Inc/certisyn-drafts

Regulatory filings

FCC Electronic Comment Filing System, PS Docket 21-479 and PS Docket 13-75. Treasury: regulations.gov docket TREAS-DO-2026-0496. SEC: comment file S7-2026-27. Federal Reserve Board: comment list for R-1899, Certisyn at FR-2026-0033-01-C18.

Research record

doi.org/10.5281/zenodo.23333369 - the joint SCITT interoperability report, with the full author list.

Adjudication integration

internetcourt.org - Internet Court, the adjudication layer Certisyn determinations feed.

LinkedIn - the public announcement by Internet Court co-founder Burak Rahil, 19 October 2026.

Membership

OpenID Foundation membership is confirmed by the Foundation at openid.net/foundation/contact.

Signing keys and transparency record

keys.certisyn.com/vao/ — active and superseded keys, with the verification procedure and worked examples.

Certificate registry

registry.certisyn.com — resolves an issued certificate without contacting Certisyn.

Trademark

USPTO serial 99720190, CERTISYN, filed 23 March 2026.

Certification

ISO/IEC 27001:2022 certificate 260626050102 and ISO 9001:2015 certificate 260626010101, issued by ARS Assessment Private Limited (CB-MS-3923), registered 26 June 2026, expiring 25 June 2029.

Partner listing

hol.org partner programme — HOL is part of the Hiero Project under Linux Foundation Decentralized Trust.