Skip to main content

ArquivoNulo Protocol

Current evaluation posture​

Framework id: arquivonulo
Source posture: owner-controlled public documentation and public GitHub implementation artifacts observed
Self-declaration posture: reconstructed from public materials; not owner-confirmed as a frozen evaluation declaration
StegVerse determination: bounded public-source reconstruction complete and updated through public implementation evidence
Public implementation posture: protocol specifications, canonical artifacts, verification tooling, and an experimental executable Query Guard implementation are publicly available
Execution-boundary posture: sequence ambiguity requires clarification
Live cross-framework test: NOT_TESTED
Replay: NOT_TESTED
Reconstruction: PARTIAL
Authority granted: none

Public implementation surfaces​

ArquivoNulo is not represented only by conceptual publications. Public GitHub repositories currently expose both specifications and executable integrity tooling:

arquivonulo369-beep/arquivonulo
  -> canonical-state, authority, ledger, verification, sealing, evidence, and structural history artifacts

arquivonulo369-beep/arquivonulo-foundation
  -> protocol registry, whitepapers, ANP specifications, governance, verification guidance, canonical manifests, signatures, and ANP-004 release artifacts

arquivonulo369-beep/arquivonulo-query-guard
  -> experimental/pre-canonical executable integrity layer implementing Merkle construction, signed snapshots, ledger validation, snapshot auditing, and proof verification

The public Query Guard README explicitly labels that implementation Experimental (Pre-Canonical). Public source availability therefore establishes a real implementation surface without establishing completeness, production activation, or equivalence to every published ArquivoNulo claim.

Publicly documented architecture​

ArquivoNulo publicly presents a protocol family centered on deterministic state anchoring, integrity validation, cryptographic proof, execution records, interdiction, and multi-agent coordination.

The public materials identify at least:

ANP-001 — Deterministic State Stasis Protocol
ANP-002 — Agent Integrity Protocol, draft v0.1-alpha
ANP-003 — Execution Ledger Protocol, canonical
ANP-004 — multi-agent coordination / sovereign ecosystem release package

ANP-002 describes an autonomous-agent integrity layer combining ANP-001 state anchoring with zero-knowledge proofs. Its declared proof statement is intended to establish that a private computation trace:

- complies with policy circuit P
- begins from an ANP-001 anchored state
- produces the declared output

The protocol also declares automatic interdiction when proof verification fails.

ANP-004 extends the framework into coordinated multi-agent execution and is relevant to interoperability because it introduces a shared execution-boundary problem across otherwise distinct actors or systems.

Initial StegVerse boundary determination​

Based only on the reviewed public materials, StegVerse currently determines ArquivoNulo to be:

A deterministic integrity, proof, execution-ledger, and interdiction architecture designed to bind execution to anchored state and declared policy representations while preserving private computation details, with later public work extending the model toward coordinated multi-agent execution.

This establishes meaningful architectural substance beyond a general claim that invalid states cannot form. It does not yet establish that every current institutional, environmental, or authority condition required for execution is independently reconstructed at the point where consequence attaches.

Execution-order ambiguity​

ANP-002 publishes the following extended state sequence:

S0 Idle
-> S1 Ingestion / Perception
-> S2 Anchoring
-> S3 Integrity Check
-> S4 Stasis Lock
-> S5 Execution / Transmission
-> S6 Validation + Proof Generation
-> S7 Proof Verification
-> SUCCESS or INTERDICTION

The same specification requires proof generation after every critical decision and interdiction on invalid proof.

That creates a decisive implementation question:

Does S5 represent a provisional execution candidate whose external effects remain withheld until S7 succeeds, or does consequence bind at S5 before proof verification?

The two interpretations are not equivalent.

provisional candidate at S5 + effect withheld until S7
  -> commit-bound prevention may be supported

external consequence binds at S5 before S7
  -> post-execution verification and interdiction

Until a direct technical artifact or live trace resolves the sequence, the execution-boundary result remains PUBLICLY_UNRESOLVED.

Integrity proof versus continuing admissibility​

A valid ArquivoNulo proof may establish faithful execution against encoded inputs and rules:

valid_proof(t)
  = trace_conforms_to_policy(t)
  AND anchored_state_matches(t)
  AND output_commitment_matches(t)

Continuing admissibility requires additional independently falsifiable terms:

admissible_continuation(t)
  = valid_proof(t)
  AND current_authority(t)
  AND applicable_policy(t)
  AND admissible_evidence(t)
  AND environmental_correspondence(t)
  AND recoverability(t)
  AND intervention_capacity(t)

Therefore:

Canonical boundary shorthand: valid proof != continuing admissibility. A second canonical shorthand is anchored state != current reality.

valid_proof(t) != continuing_admissibility(t)
operational_continuity(t) != authority_continuity(t)
anchored_state(t) != current_state_correspondence(t)
technically_realizable(t) != presently_authorized(t)

A cryptographic proof can show that an encoded proposition was satisfied. It does not, by itself, establish that the proposition remains institutionally authoritative, temporally current, or materially correspondent with reality.

Open interoperability position​

ArquivoNulo and StegVerse need not be treated as mutually exclusive architectures.

A plausible governed relationship is:

StegVerse Transition Table / admissibility reconstruction
  -> determines whether the next transition presently has standing

ArquivoNulo anchoring, proof, ledger, and interdiction
  -> proves and enforces conformance to the admitted transition representation

StegVerse Interlock
  -> preserves each system's independent authority while admitting explicitly governed evidence/state exchange

Under that model, either system could expose evidence or state to the other without making either one the other's execution authority. A governed interlock could therefore reveal complementary capability, incompatible assumptions, or improvements useful to one or both systems.

This is an interoperability hypothesis. It is not an integration claim, endorsement, certification, or assertion that either framework currently implements the other's requirements.

Independent-use posture​

StegVerse treats external frameworks as legitimate independent test surfaces when public artifacts make comparison possible. ArquivoNulo may use the StegVerse SDK, governance lanes, published evidence, and governed test surfaces independently. Likewise, StegVerse may inspect public ArquivoNulo artifacts and test interoperability propositions.

If either system materially validates, augments, or improves the other, attribution is useful provenance but is not a prerequisite for access or testing. The controlling requirement is preservation of evidence, chronology, and independent authority boundaries.

Decisive minimum test​

1. Anchor a valid state and policy representation.
2. Produce an execution candidate that initially satisfies the encoded policy circuit.
3. Hold external consequence pending proof verification, if the architecture supports doing so.
4. Change only one current governing condition: authority, delegation, evidence validity, jurisdiction, environment, or intervention reachability.
5. Attempt the next consequence-bearing transition without changing the prior anchored representation.
6. Observe whether the system independently reconstructs the changed condition before effect binds.
7. Record ALLOW, HOLD, DENY, INTERDICT, or EFFECT_ALREADY_BOUND.

Interpretation:

change independently detected before effect
  -> current-condition reconstruction supported for that variable

proof succeeds against unchanged prior representation
  -> integrity proven, current admissibility unresolved or unsupported

interdiction occurs only after effect
  -> post-consequence correction, not commit-bound prevention

insufficient evidence
  -> PUBLICLY_UNRESOLVED

What was found publicly​

FOUND
- official documentation portal
- public canonical ArquivoNulo repository
- public ArquivoNulo Foundation repository
- public experimental Query Guard implementation repository
- named ANP-001, ANP-002, ANP-003, and ANP-004 protocol/release surfaces
- deterministic state anchoring and stasis claims
- ANP-002 zero-knowledge policy-compliance proof model
- explicit state sequence from ingestion through execution, proof, verification, and interdiction
- public canonical-artifact, hash, signature, and archive claims
- executable Merkle/snapshot/ledger/proof-verification tooling in Query Guard
- automatic interdiction doctrine on invalid proof
- multi-agent coordination extension through ANP-004

NOT YET ESTABLISHED BY REVIEWED PUBLIC EVIDENCE
- frozen neutral evaluation declaration supplied directly to StegVerse
- complete live execution trace showing when external effect binds
- proof that S5 is provisional rather than consequence-bearing
- production activation of the complete published architecture
- live authority-revocation or environmental-drift fixture
- independent reconstruction of current authority after anchoring
- proof that current policy validity is established rather than inherited
- live ArquivoNulo <-> StegVerse governed interlock run

NOT YET ESTABLISHED means only that the reviewed evidence does not establish the proposition. It is not a claim that no private or additional public artifact exists.

Public sources reviewed​

https://arquivonulo369-beep.github.io/arquivonulo-foundation/
https://arquivonulo369-beep.github.io/arquivonulo-foundation/protocols/drafts/ANP-002-agent-integrity.html
https://github.com/arquivonulo369-beep/arquivonulo
https://github.com/arquivonulo369-beep/arquivonulo-foundation
https://github.com/arquivonulo369-beep/arquivonulo-query-guard

Machine-readable record​

/static/data/framework-evaluations/arquivonulo.json

Authority boundary​

public documentation != live implementation
public source != production activation
protocol integrity != execution authority
anchored representation != current reality
policy conformance != current policy validity
proof verification != institutional legitimacy
interdiction != pre-consequence prevention
technical realizability != admissibility
interoperability != merged authority
PUBLICLY_UNRESOLVED != absent, failed, or disproven
publication != certification
comparison != endorsement