Public evidence
What supports each claim.
A package on PyPI, a passing test fixture, a team-run demonstration, and an outside reproduction are different kinds of evidence. This page shows them separately and links to the underlying records.
Bulla 0.47.1
published package
17/17
conformance vectors
14/14
routed traces
0
independent witnesses
Release state
accepted by PyPI
Bulla 0.47.1
The Get Started and CLI surfaces use this artifact's command contract.
What this check cannot tell you
The command shown here comes from the package published on PyPI, not from unreleased repository code.
Technical evidence
Commands labelled published are captured from the exact artifact accepted by PyPI; repository source is not substituted for it.
repository source
Bulla 0.47.1
Release receipt · contemporaneous. Repository behavior remains separate from accepted-artifact evidence even when the version numbers match.
What this check cannot tell you
Repository source may match or lead the latest PyPI release. Publication status and receipt coverage come from PyPI and release records, not version text alone.
Release receipt coverage
The comparison set is every Bulla release accepted by PyPI. Candidate releases do not count. A receipt created when a release was published remains distinct from one reconstructed later.
29
PyPI releases
6
contemporaneous
2
reconstructed
21
missing
0
invalid
What this check cannot tell you
Coverage is calculated against the PyPI release denominator and does not count unanchored actions outside it.
ActionReceipt conformance
wire
ActionReceipt v0.2
normative format
vectors
17/17
Python checker
TypeScript
17/17
browser parity
What this check cannot tell you
The browser and packaged checker agree on the published examples. That does not show how a separate implementation or live system will behave.
Technical evidence
Passing the supplied vectors establishes fixture parity, not independent implementation or live-system correctness.
Agent Incident Packet evidence
The profile requires an exact decision/effect anchor pair for each represented protocol. Deterministic HTTP and MCP packets bind those pairs with v0.4 receipts, opaque trace artifacts, non-circular redaction records, accepted reviewer statements, corrections, and team-operated witness evidence.
Live timeline and publish receipts require conventions: []. Convention-bearing historical receipts remain opaque evidence only and cannot satisfy live occurrence or coverage. The restriction belongs to this experimental profile; ActionReceipt v0.4 remains unchanged.
experimental
maturity
2
fixtures
2/2 / 1/2
HTTP decision / effect
2/2 / 1/2
MCP decision / effect
denominator · PATH_SEPARATE_TEAM_CONTROLLED · external A/J/I/W · 0/0/0/0 · r0
Accepted denominator checkpoints authenticate the path-separated observer’s reported snapshot. They do not prove completeness or organizational independence. An accepted observer can omit rows; self-shortening remains outside packet detection.
What this check cannot tell you
The profile, deterministic fixtures, checkers, and localhost pilots are team-authored source evidence. A packet supports zero or one witness reference. Multiple-witness aggregation remains unresolved. The empty-convention rule belongs only to this experimental profile and does not change ActionReceipt v0.4; cross-runtime convention evaluation remains outside the verification contract. Denominator checkpoints authenticate what an accepted path-separated observer reported; they do not prove completeness or organizational independence, and an accepted observer can self-shorten rows. The evidence does not establish production containment, disclosure safety, external implementation parity, independent witnessing, or incident truth. External A/J/I/W and replay counts remain 0/0/0/0 and r0.
Assurance Linker evidence
The source-only profile compiles closed structured promises into evidence, authority, coverage, capital, recourse, and consequence requirements. Python and standalone Node reports agree on the deterministic synthetic corpus.
experimental
maturity
8
dossiers
9
formal invariants
0/0/0/0
external A/J/I/W
Synthetic promises and team-operated roles do not establish worldly truth, complete denominators, external collateral encumbrance, custody, collectibility, legal enforceability, organizational independence, production safety, or mainnet readiness. Reliance remains NOT_COMPUTED.
What this check cannot tell you
The profile and Trial 0.2-r5 instrument use team-authored synthetic promises, cases, expected projections, implementations, evidence, keys, witness roots, rail observations, and settlement roles. No two-mirror publication set, cold-reader calibration, or foreign checker attempt has occurred, and recruitment readiness remains blocked. Surface completeness is relative to named frozen schemas, AL-* rules, and protected fields; it does not cover every open-world interaction. Foreign authorability, independent reproduction, institutional handling, operational separation, and marginal decision value remain blocked. Recruitment is an investigator-selected, uncompensated convenience sample and does not establish economic adoptability or representative demand. Source-to-image correspondence remains NOT_COMPUTED without a reproducible rebuild. The evidence does not establish worldly truth, complete denominators, external collateral encumbrance, custody, collectibility, legal enforceability, organizational independence, production safety, actuarial calibration, or mainnet readiness. Bitcoin is an optional rail adapter and does not evaluate predicates. External A/J/I/W and replay counts remain 0/0/0/0 and r0.
Routed-inference draft
A finite single_route_single_provider profile. The deterministic bundle contains the normative profile, taxonomy, checker, reports, and 14 traces.
draft
status
14/14
traces
single route single provider
topology
full
disclosure
0
live providers
0
settlement adapters
0
external implementations
0
independent witnesses
sha256:162ce81936a3726df832aaaa7b62976ffc06dbd550a34e88ae38d6d3346d69b0
81044 bytes · receipt measurement only, not a protocol size guarantee
What this check cannot tell you
The routed profile is a local, full-disclosure, single-router/single-provider draft with no live provider, settlement adapter, or independent implementation.
$ curl -LO https://glyphstandard.com/downloads/routed-inference-profile-v0.1-draft.zip
$ unzip routed-inference-profile-v0.1-draft.zip
$ cd routed-inference-profile-v0.1-draft
$ python3 -m pip install pynacl
$ python3 check.py
# OK: 14/14 routed-inference tracesSemantic settlement
The semantic boundary and finality profiles separate world claims, model-relative entailment, and authority-bound institutional outcomes while preserving a replayable transition record.
bulla.semantic-boundary-stack/0.3-freeze
profile
internal captive foreign substrate
classification
240
captive cases
0
reviewer holdouts
60/60 expected
exit algebra
176 cases
boundary families
blocked missing external participants
external replay
boundary specification · sha256:53dd6f5456e52032f0e69a3097cd9928bd972cca0d52502c2c013739e5ba25fe
finality specification · sha256:ba3a8eddca99ac208d62d96df59b89ede9d040b87c71691f1a251b00763388d6
evaluation report · sha256:d34910ad7ec16e30d6984f75db332dcf71efbfc056aaeb7b438e7da608cf3746
reviewer-originated hidden cases not created
independent clean-room implementation not observed
found-data adjudication not performed
no production settlement or legal-validity evidence
GitHub runners and the sprint signer are not independent witnesses
What this check cannot tell you
The claim flow is a finite captive research profile. It binds authorized institutional transitions; it does not establish worldly truth, legal validity, production settlement, custody, or independent forum behavior.
Witness and operator plurality
1
operated logs
0
ActionReceipt witnesses
0
independent witnesses
draft
operator manifest
What this check cannot tell you
An operated composition-deed log is not independent ActionReceipt witness plurality; the current independent-witness count is zero.
Witnessing preserves a receipt outside its issuer and makes inclusion or equivocation claims testable against authenticated log evidence.
What this check cannot tell you
Witness evidence establishes what entered a witnessed history; it does not prove the underlying execution occurred or reveal omitted actions.
The routed reports distinguish conveyed recourse terms from reachability, which remains unverified.
What this check cannot tell you
A consistently conveyed remedy adapter establishes recourse terms, not that a forum, remedy, or settlement path is operational.