ziros-proof-honesty

Name: ziros-proof-honesty
Availability: InStock
Author: anubisquantumcipher

Enforces proof and evidence type boundaries in ZirOS verification workflows.

Updated Mar 27, 2026

Search Tags:#verification #evidence #honesty #boundaries #proof #attestation #ziros

Ready to run

npx skills add https://github.com/AnubisQuantumCipher/ziros --skill ziros-proof-honesty

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ziros-proof-honesty
Source: https://github.com/AnubisQuantumCipher/ziros/tree/main/.codex/skills/ziros-proof-honesty
Command: npx skills add https://github.com/AnubisQuantumCipher/ziros --skill ziros-proof-honesty

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ZirOS proof honesty ensures separated boundaries between different evidence types and attestation claims, reducing risk of misinterpretation and leakage.

Core Features & Use Cases

Enforces explicit separation between trusted and advisory evidence in verification workflows.
Guides maintainers and auditors to preserve model-only vs. attested data boundaries across lane configurations.
Useful for teams implementing rigorous provenance and chain-of-custody for zero-knowledge proofs.

Quick Start

Configure the ZirOS proof honesty policy in your deployment and run the verifier in a test environment to validate boundary rules.

Frequently Asked Questions about ziros-proof-honesty

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What is proof boundary separation in zero-knowledge verification workflows?▼

It enforces explicit boundaries between trusted and advisory evidence in zero-knowledge verification workflows. It preserves model-only versus attested data boundaries across lane configurations to reduce misinterpretation and leakage risks.

How do I keep attestation and model-only data boundaries explicit in a verification ledger?▼

Apply proof honesty policies to your verification ledger to keep attestation and model-only data boundaries explicit. This enforces clear separation between evidence types and fails closed on lane downgrade to maintain chain-of-custody integrity.

How to configure ZirOS proof honesty policies for attestations?▼

Configure the ZirOS proof honesty policy in your deployment and run the verifier in a test environment to validate boundary rules. This ensures proper proof orchestration and attestation boundary enforcement before production use.

Why does my verification workflow fail closed on lane downgrade?▼

Verification workflows fail closed on lane downgrade to satisfy proof honesty requirements. This mechanism prevents unauthorized boundary crossings between trusted protocol TCB and hypothesis-carried evidence, ensuring verification integrity.

Can I use this for delegated and metadata-only data across truth surfaces?▼

Yes, it applies to delegated and metadata-only data across truth surfaces. It guides maintainers and auditors to preserve model-only versus attested data boundaries across lane configurations in the verification ledger.

What are the limitations of relying on advisory evidence in proof orchestration?▼

Advisory evidence must remain explicitly separated from trusted evidence in proof orchestration. Relying on advisory evidence without enforced boundaries risks misinterpretation and data leakage across the verification ledger.