Page Title: Lawchain Compliance Ledger Summary: Lawchain is the compliance-focused ledger that tracks regulatory obligations, oracle answers, and audit trails via receipts. It integrates with the proof system to ensure every compliance answer has a cryptographic backbone, and it is designed to speak the language of EU AI Act, GDPR, NIS2, and future frameworks. Key Findings: - Oracle answers are validated against a schema before being recorded. - Each answer is hashed and bound into a receipt, linking legal semantics to proofs. - Federation metrics allow multi-node Lawchain sync across the mesh. - Policy evaluation is driven by JSON inputs and produces JSON results for downstream tools. Components: - Lawchain Core Ledger (append-only compliance scroll). - Oracle Answer Validator (schema enforcement). - Compliance Scroll store (receipt logs). - Federation Metrics emitter. - Policy Evaluator (rule engine). Oracle Answer Schema (vm_oracle_answer_v1): ```json { "question": "string", "answer_text": "string", "citations": [{ "document_id": "string", "framework": "string", "excerpt": "string" }], "compliance_flags": { "gdpr_relevant": true, "ai_act_relevant": false, "nis2_relevant": true }, "gaps": ["string"], "insufficient_context": false, "confidence": "high" } ``` Workflows / Pipelines: - Compliance Q&A: 1. Operator (or system) asks Lawchain a question. 2. RAG/Retrieve context from policy docs and regulations. 3. LLM generates an answer draft. 4. Answer is validated against vm_oracle_answer_v1 schema. 5. Hash (Blake3 over canonical JSON) computed and receipt generated. 6. Receipt anchored via proof system and stored in Lawchain. Metrics Files (examples under /tmp/): | File | Purpose | |-------------------------|----------------------------| | lawchain_federate.out | Federation sync output | | lawchain_federate.err | Federation errors | | lawchain_metrics.out | Metrics/logging output | | policy_eval_out.json | Policy evaluation results | | policy_input.json | Policy evaluation input | Security Notes: - Answer hash computed as blake3(json.dumps(answer, sort_keys=True)). - Receipts bind answer content, timestamps, and possibly node identity. - gaps and insufficient_context prevent fake certainty in legal answers. - Citations must reference real sources, enabling audit of answer provenance. Compliance Frameworks Tracked: - GDPR – data protection and subject rights. - EU AI Act – risk classification, obligations, and logs. - NIS2 – network and information security. - Custom extensions can map additional frameworks (e.g., SOC2, ISO 27001). Dependencies: - Lawchain service. - Oracle corpus indexed (policies, regulations, internal docs). - Blake3 and JSON schema validator. - Integration with VaultMesh proof spine for receipts and anchoring.