Bounded delegation
Signed owner–agent binding, exact scope, audience, resource and payload. Owner approval can be mandatory. No implicit Agent→Agent delegation.
HUMAN SIGNAL · PUBLIC RESEARCH LAB
Inspect the permission, verify the signatures, enforce the exact effect. COHIBA SI explores human authority over autonomous-agent actions—not a claim to control every AI system.
Protected SQL effect ⇒ valid human authority at commit
Signed owner–agent binding, exact scope, audience, resource and payload. Owner approval can be mandatory. No implicit Agent→Agent delegation.
Shared PostgreSQL locks serialize local revocation and protected writes. Replay consumption and effects commit together; expired authority rolls back at COMMIT.
Inspect database tests ↗Ed25519 plus hash-based SLH-DSA-SHA2-128f for every issuer, owner and agent proof. PQ keys are pinned by the operator. No classical-only fallback.
RUN CRYPTOGRAPHY, NOT AN ANIMATION
The same portable signature module used by the Node verifier runs in a local Worker. A passing attack test means the altered proof was rejected.
These are historical, synthetic fixtures with publicly known test secrets. The browser checks signatures—not live identity, database revocation or business execution. The fixture is expired for live authorization. executionAuthorized: false.
Nothing has run yet. No account, funds or real private keys are needed.
| Check | Test | Verifier verdict | Your device |
|---|
The larger signature is a real tradeoff: 17,088 bytes per SLH-DSA signature. Timings are measured locally, not production benchmarks. No signing or authorization endpoint is exposed by this lab.
Run the historical full-chain inspection without a COH token, COHIBA account, Railway connection or blockchain wallet.
npm ci node examples/hs2/verify.mjs node --test test/hs2-verifier.test.mjs test/authority-commit-gate.test.mjs
Node ≥22. Native PostgreSQL testing uses TEST_DATABASE_URL; the local fallback uses embedded PGlite. Fixture-provided trust and evaluation time are for tests only. Real services must derive policy and pin keys themselves.
| Stage | Capability | Evidence / remaining boundary |
|---|---|---|
| Reference implementation | Independent HS/1 verifier, local SQL revocation, replay, commit deadline | PR #52; only effects integrated through the gate are protected. |
| Experimental HS/2 | Mandatory dual signatures, pinned PQ keys, browser lab | Adversarial tests; not automatically enabled on production authorization routes. |
| Next evidence gate | Independent crypto review, cross-implementation vectors, controlled key enrollment/rotation | Not complete. The implementation and HS/2 composition need their own assessment. |
| Research / future | Secure-channel migration, multi-service revocation, hardware signing, chain-compatible PQ enforcement | Not implemented by HS/2. Wallets and chains retain their own security assumptions. |
No blanket “AI-proof” or “quantum-proof” guarantee. No biological uniqueness proof, global instantaneous revocation, unlinkability, public-key encryption upgrade or atomic blockchain delivery. HS/2 uses a standardized SLH-DSA parameter set, but this software is not a FIPS-validated module and its hybrid protocol is not a ratified standard.