Total Blocks
—
Verified
—
Unverifiable Legacy
—
Errors
—
Chain Status
—
Genesis
—
Schema
004
Governance Directive Composer
Run taking longer than expected. Check nginx proxy_read_timeout on server.
Governance runs take 30-50 seconds. nginx proxy_read_timeout must be >= 90s.
Result
Core fields
No response.
Confidence bar
Copy IDs
Vendor breakdown — click to expand
No vendor results.
Cross-audit detail — click to expand
No crossAudit object.
Raw governance JSON
No raw response.
Help
POST /api/governance/run (Bearer auth)
Body: { instruction, governanceClass, terminationMode, operatorId, enableVoice }
nginx proxy_read_timeout must be >= 90s.
Last restored run
None.
Guardrail notes
- nginx proxy_read_timeout >= 90s required.
- Gateway secret required for protected endpoints.
- Vendors: Anthropic, OpenAI, Gemini only.
Chain verify
valid
-
chainDepth
-
genesis
hidden pending verifier reconciliation
blockCount
-
timestamp
-
Raw chain verify JSON
No chain data.
Evidence lookup
Manual seal
Evidence output
No evidence loaded.
Browse results
Set filters in the sidebar Audit Filters and click Search. Click a result row to load its block seal below.
Block seal — SHA-256 hash & canonical input
Load a marker above. The seal is the SHA-256 of the canonical (key-sorted) JSON shown below. Click Verify hash to recompute it client-side and confirm tamper-evidence.
marker_id
—
record_type
—
governance_class
—
audit_result
—
previous_marker_hash
—
block_hash
—
verification
UNVERIFIED
Canonical hash_input
This is the exact byte sequence fed to SHA-256 to produce block_hash. An external auditor with this string and any SHA-256 tool can verify the seal independently.
—