# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-10-06T11:48:49Z", "synthesisSha256": "73cb41e3ab9a8617359a8434b686d5251cac81a697c4f29e65c0ab4a5d1d81bf", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-POL-019", "registryId": "vr.wm-pol-019", "name": "Legal Filing / Pleading", "version": "0.1.0-reviewable-draft", "previousVersions": [], "entryKind": "entity", "family": "World Models", "category": "Society, people and institutions", "industry": [ "Cross-industry" ], "domain": [ "SOC.POL.FIL" ], "tags": [ "legal", "filing", "pleading", "soc.pol.fil" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-pol-019-legal-filing-pleading/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-pol-019", "model": { "registry_id": "vr.wm-pol-019", "model_id": "WM-POL-019", "name": "Legal Filing / Pleading", "entry_kind": "entity", "purpose": "Represent one identifiable procedural document record, its controlled revisions, and evidence about presentation to a court or tribunal and service.", "scope_statement": "A proposed format-neutral entity for a pleading or other procedural filing document, including preparation, submission attempts, court-record references and later revisions. The document remains distinct from an electronic filing transaction, which can carry multiple documents. Selected civil examples ground questions rather than a universal executable legal workflow.", "in_scope": [ "Document identity and classification, intended or assigned case and court references, profile and custodian", "Filer and signer capacities, asserted positions and requested relief, attachment references and document-specific formal checks", "Evidence of submission, receipt, review, docketing, deadline assessment, service and amendment authority", "Controlled renditions, confidentiality, redaction, provenance and local retention-policy references" ], "out_of_scope": [ "Court case lifecycle, adjudication, merits, determination of evidence admissibility and judicial remedies", "Electronic filing transaction engine, actual signing, filing, service, fee payment or automated legal deadline execution", "Independent evidence exhibit masters, party identity masters, representation mandates and court authority masters", "Universal rules for criminal, family, appellate, arbitration, administrative or cross-border proceedings; these require separate profiles" ], "boundary_notes": [ { "neighbor": "WM-POL-009 Court case", "distinction": "The incoming candidate CONTAINS edge is respected as case-to-document containment. This record references its parent and does not own the case lifecycle. An originating document can have a pending case number; record intended forum and reconcile later.", "source_refs": [ "SRC-001", "SRC-007" ] }, { "neighbor": "Electronic filing transaction and message", "distinction": "An envelope or transaction can carry several documents and have several messages. It is not this document entity, and a transaction identifier is a typed correlation reference rather than the sole document key.", "source_refs": [ "SRC-007" ] }, { "neighbor": "Evidence exhibit and court order", "distinction": "Attachments and orders are independently identified references. A filing can cite evidence or request relief without making the evidence true or producing a judicial disposition.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] }, { "neighbor": "Administrative application and general correspondence", "distinction": "Routing and applicable procedural profile decide whether a document belongs here; contested status is not an invariant. No administrative case or correspondence lifecycle is imported.", "source_refs": [ "SRC-001", "SRC-007" ] }, { "neighbor": "Registry record plane", "distinction": "The registry standalone-mm label classifies the catalogue entry. The subject kind is entity because document identity persists across events. No legacy_alias or existing_spec_ref is registered.", "source_refs": [ "SRC-007", "SRC-008" ] } ] }, "sources": [ { "id": "SRC-001", "title": "Federal Rules of Civil Procedure", "organization": "Administrative Office of the United States Courts", "url": "https://www.uscourts.gov/sites/default/files/document/federal-rules-of-civil-procedure.pdf", "version_or_date": "December 1, 2025 edition; selected rules reviewed on 2026-10-06", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T11:47:44Z", "relevance": "Rules 5, 5.2, 6, 7, 8, 10 and 11: civil filing, document category, time, form, signature and protection examples. No local-rule or universal applicability claim." }, { "id": "SRC-002", "title": "Civil Procedure Rules Part 16 - Statements of Case", "organization": "Ministry of Justice", "url": "https://www.justice.gov.uk/courts/procedure-rules/civil/rules/part16", "version_or_date": "Live page observed 2026-10-06; current effective consolidation not independently certified", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T11:47:44Z", "relevance": "Rules 16.2-16.5: content, relief, value and responses in England and Wales civil statements of case; profile-specific, not universal pleading rules." }, { "id": "SRC-003", "title": "Civil Procedure Rules Part 22 - Statements of Truth", "organization": "Ministry of Justice", "url": "https://www.justice.gov.uk/courts/procedure-rules/civil/rules/part22", "version_or_date": "Live page observed 2026-10-06; effective-version verification held", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T11:47:44Z", "relevance": "Rules 22.1-22.2: verification, signer capacities, document identification and unverified statements; a signed belief is not adjudicated truth." }, { "id": "SRC-004", "title": "Civil Procedure Rules Part 17 - Amendments to Statements of Case", "organization": "Ministry of Justice", "url": "https://www.justice.gov.uk/courts/procedure-rules/civil/rules/part17", "version_or_date": "Live page observed 2026-10-06; effective-version verification held", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T11:47:44Z", "relevance": "Rules 17.1-17.3: amendment authority and service context; technical revision does not confer permission to amend." }, { "id": "SRC-005", "title": "Civil Procedure Rules Part 6 - Service of Documents", "organization": "Ministry of Justice", "url": "https://www.justice.gov.uk/courts/procedure-rules/civil/rules/part06", "version_or_date": "Live page observed 2026-10-06; effective-version verification held", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T11:47:44Z", "relevance": "Selected sections II-IV, especially 6.21-6.29: recipients, addresses, methods, deemed service and proof. Cross-border implementation is deferred." }, { "id": "SRC-006", "title": "Civil Procedure Rules Part 5 - Court Documents", "organization": "Ministry of Justice", "url": "https://www.justice.gov.uk/courts/procedure-rules/civil/rules/part05", "version_or_date": "Live page observed 2026-10-06; effective-version verification held", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T11:47:44Z", "relevance": "Rules 5.2-5.4D: document preparation and differentiated court-record access; public statements do not automatically expose their attachments." }, { "id": "SRC-007", "title": "Electronic Court Filing Version 5.0", "organization": "OASIS Open", "url": "https://docs.oasis-open.org/legalxml-courtfiling/ecf/v5.0/cs01/ecf-v5.0-cs01.pdf", "version_or_date": "Committee Specification 01, 18 April 2019", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T11:47:44Z", "relevance": "Sections 6.1 and 6.2 distinguish review, docketing and service operations and case, transaction, message and document identifiers. Conceptual alignment only." }, { "id": "SRC-008", "title": "PROV-O: The PROV Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/prov-o/", "version_or_date": "Recommendation, 30 April 2013; version metadata recheck required before integration", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T11:47:44Z", "relevance": "Entity, activity, attribution, derivation and revision concepts support proposed lineage design, without certifying legal authenticity or authority." } ], "structure": { "bundles": [ { "id": "fil-b-identity", "name": "Identity and procedural setting", "description": "Identify the document and the rule context used to interpret it.", "rationale": "Stable identity must survive external numbering and jurisdiction-specific terminology.", "source_refs": [ "SRC-001", "SRC-007" ], "layers": [ { "id": "fil-l-identity", "name": "Document identity and case binding context", "description": "Questions and evidence for document identity and case binding, limited to this filing document.", "source_refs": [ "SRC-001", "SRC-007" ], "findings": [ { "id": "fil-f-identity", "name": "Document identity and case binding", "description": "Proposed document identity separates drafts, court aliases, renditions and transaction references. The parent case may be unresolved before initiation; matching requires evidence.", "source_refs": [ "SRC-001", "SRC-007" ], "questions": [ { "id": "fil-q-identity-1", "kind": "identity", "text": "Which master namespace and document key identify this record before and after court numbering?", "answer_data": [ "master namespace", "document key", "aliases", "reconciliation evidence" ] }, { "id": "fil-q-identity-2", "kind": "relationship", "text": "Which existing or intended case and forum does this document belong to, and what remains unresolved?", "answer_data": [ "parent case reference", "intended forum", "case assignment status", "linkage evidence" ] }, { "id": "fil-q-identity-3", "kind": "classification", "text": "Which procedural document class applies, and is it a pleading, motion or another paper under the selected profile?", "answer_data": [ "document class", "classification vocabulary version", "profile rule", "classification uncertainty" ] } ], "data_elements": [ { "id": "fil-de-identity-1", "name": "master namespace", "description": "Candidate answer group: master namespace; document key; aliases; reconciliation evidence. Preserve unknown, disputed and not-applicable states with source and observer; nested instance schema remains a profile task.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] }, { "id": "fil-de-identity-2", "name": "parent case reference", "description": "Candidate answer group: parent case reference; intended forum; case assignment status; linkage evidence. Preserve unknown, disputed and not-applicable states with source and observer; nested instance schema remains a profile task.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] }, { "id": "fil-de-identity-3", "name": "document class", "description": "Candidate answer group: document class; classification vocabulary version; profile rule; classification uncertainty. Preserve unknown, disputed and not-applicable states with source and observer; nested instance schema remains a profile task.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] } ], "artifacts": [ { "id": "fil-art-identity", "name": "Document identity and alias register", "description": "Proposed governed evidence record for document identity and case binding. It may be a reference or structured record, not necessarily a separate file.", "media_or_form": [ "Structured record or reference to controlled document" ], "serial": true, "identity_strategy": "Authoritative master-system artifact ID and namespace first; otherwise governed IRI, then local UUID or ULID. Preserve revision and rendition identities; dates and digests alone are not identity.", "source_refs": [ "SRC-001", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "fil-l-profile", "name": "Applicable procedural profile context", "description": "Questions and evidence for applicable procedural profile, limited to this filing document.", "source_refs": [ "SRC-001", "SRC-007" ], "findings": [ { "id": "fil-f-profile", "name": "Applicable procedural profile", "description": "A jurisdiction and proceeding profile selects terminology and applicable requirements. Physical quantities are inapplicable to the abstract record, but class, language, state and dates are direct properties.", "source_refs": [ "SRC-001", "SRC-007" ], "questions": [ { "id": "fil-q-profile-1", "kind": "requirement", "text": "Which court rules, local directions and orders govern this document for the relevant procedural date?", "answer_data": [ "jurisdiction", "proceeding type", "rule and order references", "effective interval" ] }, { "id": "fil-q-profile-2", "kind": "ownership", "text": "Which custodian controls the draft and court-record copies, and which authority can resolve a disagreement?", "answer_data": [ "copy scope", "accountable custodian", "master authority", "escalation route" ] }, { "id": "fil-q-profile-3", "kind": "interoperability", "text": "Which exchange profile and code mappings preserve this document type and explicitly report unmapped qualifiers?", "answer_data": [ "exchange profile version", "type mapping", "language and rendition requirements", "loss report" ] } ], "data_elements": [ { "id": "fil-de-profile-1", "name": "jurisdiction", "description": "Candidate answer group: jurisdiction; proceeding type; rule and order references; effective interval. Preserve unknown, disputed and not-applicable states with source and observer; nested instance schema remains a profile task.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] }, { "id": "fil-de-profile-2", "name": "copy scope", "description": "Candidate answer group: copy scope; accountable custodian; master authority; escalation route. Preserve unknown, disputed and not-applicable states with source and observer; nested instance schema remains a profile task.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] }, { "id": "fil-de-profile-3", "name": "exchange profile version", "description": "Candidate answer group: exchange profile version; type mapping; language and rendition requirements; loss report. Preserve unknown, disputed and not-applicable states with source and observer; nested instance schema remains a profile task.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] } ], "artifacts": [ { "id": "fil-art-profile", "name": "Procedural profile binding", "description": "Proposed governed evidence record for applicable procedural profile. It may be a reference or structured record, not necessarily a separate file.", "media_or_form": [ "Structured record or reference to controlled document" ], "serial": true, "identity_strategy": "Authoritative master-system artifact ID and namespace first; otherwise governed IRI, then local UUID or ULID. Preserve revision and rendition identities; dates and digests alone are not identity.", "source_refs": [ "SRC-001", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "fil-b-authorship", "name": "Authorship and asserted position", "description": "Record who presents the document and what they assert or request.", "rationale": "Identity, authority, signed verification and substantive position answer different questions.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "layers": [ { "id": "fil-l-authority", "name": "Filer and verification authority context", "description": "Questions and evidence for filer and verification authority, limited to this filing document.", "source_refs": [ "SRC-001", "SRC-003" ], "findings": [ { "id": "fil-f-authority", "name": "Filer and verification authority", "description": "Record filer, represented party and signer capacity separately. Self-representation and other permitted capacities cannot be excluded; signature or verification does not establish factual truth.", "source_refs": [ "SRC-001", "SRC-003" ], "questions": [ { "id": "fil-q-authority-1", "kind": "authority", "text": "In what capacity does each filer or signatory act, and what evidence supports that capacity for this document?", "answer_data": [ "party reference", "filer reference", "signer reference", "capacity and mandate evidence" ] }, { "id": "fil-q-authority-2", "kind": "validation", "text": "Which signature or statement-of-truth requirement applies to this revision, and what review result or exception is recorded?", "answer_data": [ "verification requirement", "signed revision", "signature evidence", "reviewer result", "exception basis" ] }, { "id": "fil-q-authority-3", "kind": "exception", "text": "How is an absent, disputed or inaccessible signature referred for authorized correction without silently treating the document as verified?", "answer_data": [ "verification defect", "accessibility support", "responsible reviewer", "correction reference", "unresolved status" ] } ], "data_elements": [ { "id": "fil-de-authority-1", "name": "party reference", "description": "Candidate answer group: party reference; filer reference; signer reference; capacity and mandate evidence. Preserve unknown, disputed and not-applicable states with source and observer; nested instance schema remains a profile task.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "fil-de-authority-2", "name": "verification requirement", "description": "Candidate answer group: verification requirement; signed revision; signature evidence; reviewer result; exception basis. Preserve unknown, disputed and not-applicable states with source and observer; nested instance schema remains a profile task.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "fil-de-authority-3", "name": "verification defect", "description": "Candidate answer group: verification defect; accessibility support; responsible reviewer; correction reference; unresolved status. Preserve unknown, disputed and not-applicable states with source and observer; nested instance schema remains a profile task.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] } ], "artifacts": [ { "id": "fil-art-authority", "name": "Authorship and verification evidence", "description": "Proposed governed evidence record for filer and verification authority. It may be a reference or structured record, not necessarily a separate file.", "media_or_form": [ "Structured record or reference to controlled document" ], "serial": true, "identity_strategy": "Authoritative master-system artifact ID and namespace first; otherwise governed IRI, then local UUID or ULID. Preserve revision and rendition identities; dates and digests alone are not identity.", "source_refs": [ "SRC-001", "SRC-003" ] } ], "inline_only_rationale": null } ] }, { "id": "fil-l-position", "name": "Assertions, responses and requested relief context", "description": "Questions and evidence for assertions, responses and requested relief, limited to this filing document.", "source_refs": [ "SRC-001", "SRC-002" ], "findings": [ { "id": "fil-f-position", "name": "Assertions, responses and requested relief", "description": "Capture positions as attributed statements. Allegations, admissions, denials and requests must remain distinct from findings of the court; requested relief is not an award.", "source_refs": [ "SRC-001", "SRC-002" ], "questions": [ { "id": "fil-q-position-1", "kind": "composition", "text": "Which numbered statements or claim components form this document and which earlier statements do they answer?", "answer_data": [ "statement identifiers", "section order", "response targets", "incorporation references" ] }, { "id": "fil-q-position-2", "kind": "evidence", "text": "Which propositions are alleged, admitted, denied or left for proof, and whose position is each?", "answer_data": [ "proposition text reference", "asserting party", "response classification", "supporting citation", "dispute status" ] }, { "id": "fil-q-position-3", "kind": "measurement", "text": "What relief or amount is requested, including currency and calculation basis where relevant, without representing it as awarded?", "answer_data": [ "relief request", "claimed amount and currency", "interest basis", "calculation period", "valuation uncertainty" ] } ], "data_elements": [ { "id": "fil-de-position-1", "name": "statement identifiers", "description": "Candidate answer group: statement identifiers; section order; response targets; incorporation references. Preserve unknown, disputed and not-applicable states with source and observer; nested instance schema remains a profile task.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "fil-de-position-2", "name": "proposition text reference", "description": "Candidate answer group: proposition text reference; asserting party; response classification; supporting citation; dispute status. Preserve unknown, disputed and not-applicable states with source and observer; nested instance schema remains a profile task.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "fil-de-position-3", "name": "relief request", "description": "Candidate answer group: relief request; claimed amount and currency; interest basis; calculation period; valuation uncertainty. Preserve unknown, disputed and not-applicable states with source and observer; nested instance schema remains a profile task.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] } ], "artifacts": [ { "id": "fil-art-position", "name": "Attributed position and relief index", "description": "Proposed governed evidence record for assertions, responses and requested relief. It may be a reference or structured record, not necessarily a separate file.", "media_or_form": [ "Structured record or reference to controlled document" ], "serial": true, "identity_strategy": "Authoritative master-system artifact ID and namespace first; otherwise governed IRI, then local UUID or ULID. Preserve revision and rendition identities; dates and digests alone are not identity.", "source_refs": [ "SRC-001", "SRC-002" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "fil-b-content", "name": "Document content and readiness", "description": "Connect controlled content to supporting materials and profile checks.", "rationale": "Attachments and technical readiness must not be mistaken for substantive acceptance.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007", "SRC-008" ], "layers": [ { "id": "fil-l-attachments", "name": "Renditions and supporting references context", "description": "Questions and evidence for renditions and supporting references, limited to this filing document.", "source_refs": [ "SRC-001", "SRC-007", "SRC-008" ], "findings": [ { "id": "fil-f-attachments", "name": "Renditions and supporting references", "description": "The filing has controlled document renditions and typed links to exhibits, authorities and other documents. A referenced artifact retains its own master and access conditions.", "source_refs": [ "SRC-001", "SRC-007", "SRC-008" ], "questions": [ { "id": "fil-q-attachments-1", "kind": "composition", "text": "Which lead rendition, attachments and cited materials belong to this revision, and which are separately mastered?", "answer_data": [ "rendition reference", "attachment role", "exhibit master reference", "citation locator", "revision link" ] }, { "id": "fil-q-attachments-2", "kind": "quality", "text": "What evidence checks each cited authority or attachment for existence, legibility and correct association with the asserted proposition?", "answer_data": [ "verification actor", "checked locator", "legibility result", "proposition link", "unresolved citation" ] }, { "id": "fil-q-attachments-3", "kind": "provenance", "text": "Which transformations produced the filed, translated or redacted rendition, and how is its relationship to the source preserved?", "answer_data": [ "source rendition", "derived rendition", "transformation activity", "content digest", "translator or redactor attribution" ] } ], "data_elements": [ { "id": "fil-de-attachments-1", "name": "rendition reference", "description": "Candidate answer group: rendition reference; attachment role; exhibit master reference; citation locator; revision link. Preserve unknown, disputed and not-applicable states with source and observer; nested instance schema remains a profile task.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-007", "SRC-008" ] }, { "id": "fil-de-attachments-2", "name": "verification actor", "description": "Candidate answer group: verification actor; checked locator; legibility result; proposition link; unresolved citation. Preserve unknown, disputed and not-applicable states with source and observer; nested instance schema remains a profile task.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-007", "SRC-008" ] }, { "id": "fil-de-attachments-3", "name": "source rendition", "description": "Candidate answer group: source rendition; derived rendition; transformation activity; content digest; translator or redactor attribution. Preserve unknown, disputed and not-applicable states with source and observer; nested instance schema remains a profile task.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-007", "SRC-008" ] } ], "artifacts": [ { "id": "fil-art-attachments", "name": "Rendition and attachment manifest", "description": "Proposed governed evidence record for renditions and supporting references. It may be a reference or structured record, not necessarily a separate file.", "media_or_form": [ "Structured record or reference to controlled document" ], "serial": true, "identity_strategy": "Authoritative master-system artifact ID and namespace first; otherwise governed IRI, then local UUID or ULID. Preserve revision and rendition identities; dates and digests alone are not identity.", "source_refs": [ "SRC-001", "SRC-007", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "fil-l-readiness", "name": "Formal and technical readiness context", "description": "Questions and evidence for formal and technical readiness, limited to this filing document.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007" ], "findings": [ { "id": "fil-f-readiness", "name": "Formal and technical readiness", "description": "A proposed local readiness assessment records actual profile criteria and failures. Its successful result grants no filing permission or legal sufficiency and is distinct from court review.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007" ], "questions": [ { "id": "fil-q-readiness-1", "kind": "constraint", "text": "Which form, caption, language, format and attachment requirements have been checked for the selected filing route?", "answer_data": [ "requirement reference", "caption fields", "language", "format constraints", "check result" ] }, { "id": "fil-q-readiness-2", "kind": "process", "text": "Which fee assessment, exemption or waiver evidence is required for this submission route and who resolves an unknown result?", "answer_data": [ "fee requirement", "assessed amount and currency", "waiver reference", "payment evidence reference", "responsible role" ] }, { "id": "fil-q-readiness-3", "kind": "decision", "text": "Which unresolved readiness defects prevent local approval and what authorized disposition records their resolution?", "answer_data": [ "defect list", "severity", "local approval status", "reviewer", "correction or exception evidence" ] } ], "data_elements": [ { "id": "fil-de-readiness-1", "name": "requirement reference", "description": "Candidate answer group: requirement reference; caption fields; language; format constraints; check result. Preserve unknown, disputed and not-applicable states with source and observer; nested instance schema remains a profile task.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-006", "SRC-007" ] }, { "id": "fil-de-readiness-2", "name": "fee requirement", "description": "Candidate answer group: fee requirement; assessed amount and currency; waiver reference; payment evidence reference; responsible role. Preserve unknown, disputed and not-applicable states with source and observer; nested instance schema remains a profile task.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-006", "SRC-007" ] }, { "id": "fil-de-readiness-3", "name": "defect list", "description": "Candidate answer group: defect list; severity; local approval status; reviewer; correction or exception evidence. Preserve unknown, disputed and not-applicable states with source and observer; nested instance schema remains a profile task.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "fil-art-readiness", "name": "Readiness assessment record", "description": "Proposed governed evidence record for formal and technical readiness. It may be a reference or structured record, not necessarily a separate file.", "media_or_form": [ "Structured record or reference to controlled document" ], "serial": true, "identity_strategy": "Authoritative master-system artifact ID and namespace first; otherwise governed IRI, then local UUID or ULID. Preserve revision and rendition identities; dates and digests alone are not identity.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "fil-b-filing", "name": "Filing events and time assertions", "description": "Preserve observed submission events and supported time assessments.", "rationale": "Receipt, review, docketing and legal timeliness require separate evidence.", "source_refs": [ "SRC-001", "SRC-007" ], "layers": [ { "id": "fil-l-submission", "name": "Submission and court-record status context", "description": "Questions and evidence for submission and court-record status, limited to this filing document.", "source_refs": [ "SRC-007" ], "findings": [ { "id": "fil-f-submission", "name": "Submission and court-record status", "description": "Document-specific status references are correlated with transaction and message records. Partial review results remain per document; a receipt alone cannot establish docketing, service or merits.", "source_refs": [ "SRC-007" ], "questions": [ { "id": "fil-q-submission-1", "kind": "event", "text": "Which submission attempt carried this exact revision and which receipt, review and docket events are evidenced separately?", "answer_data": [ "attempt reference", "transaction and message IDs", "submitted revision", "receipt event", "review event", "docket reference" ] }, { "id": "fil-q-submission-2", "kind": "state", "text": "What is the latest supported document status, including partial acceptance, rejection or unresolved conflicting responses?", "answer_data": [ "document status", "source authority", "rejection reason", "competing status assertions", "observed time" ] }, { "id": "fil-q-submission-3", "kind": "exception", "text": "How are duplicate transmissions or resubmissions correlated without merging distinct documents or assuming the earlier attempt succeeded?", "answer_data": [ "idempotency or correlation key", "prior attempt", "document digest comparison", "duplicate decision", "reconciliation reason" ] } ], "data_elements": [ { "id": "fil-de-submission-1", "name": "attempt reference", "description": "Candidate answer group: attempt reference; transaction and message IDs; submitted revision; receipt event; review event; docket reference. Preserve unknown, disputed and not-applicable states with source and observer; nested instance schema remains a profile task.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-007" ] }, { "id": "fil-de-submission-2", "name": "document status", "description": "Candidate answer group: document status; source authority; rejection reason; competing status assertions; observed time. Preserve unknown, disputed and not-applicable states with source and observer; nested instance schema remains a profile task.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-007" ] }, { "id": "fil-de-submission-3", "name": "idempotency or correlation key", "description": "Candidate answer group: idempotency or correlation key; prior attempt; document digest comparison; duplicate decision; reconciliation reason. Preserve unknown, disputed and not-applicable states with source and observer; nested instance schema remains a profile task.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-007" ] } ], "artifacts": [ { "id": "fil-art-submission", "name": "Submission and status evidence register", "description": "Proposed governed evidence record for submission and court-record status. It may be a reference or structured record, not necessarily a separate file.", "media_or_form": [ "Structured record or reference to controlled document" ], "serial": true, "identity_strategy": "Authoritative master-system artifact ID and namespace first; otherwise governed IRI, then local UUID or ULID. Preserve revision and rendition identities; dates and digests alone are not identity.", "source_refs": [ "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "fil-l-time", "name": "Deadline and legal-time assessment context", "description": "Questions and evidence for deadline and legal-time assessment, limited to this filing document.", "source_refs": [ "SRC-001", "SRC-005" ], "findings": [ { "id": "fil-f-time", "name": "Deadline and legal-time assessment", "description": "Record supplied legal-time assessments with their rule and trigger. Event time, receipt time, deemed time and observation time remain distinct; no universal calendar or deadline engine is supplied.", "source_refs": [ "SRC-001", "SRC-005" ], "questions": [ { "id": "fil-q-time-1", "kind": "temporal", "text": "Which trigger, rule, timezone, calendar and court order support the asserted due time for this filing?", "answer_data": [ "trigger evidence", "time-computation rule", "legal timezone", "holiday calendar version", "due-time assertion" ] }, { "id": "fil-q-time-2", "kind": "validation", "text": "Who assessed timeliness against which filing event and how are disputed timestamps, outages or extensions recorded?", "answer_data": [ "assessment actor", "selected filing event", "precision", "outage evidence", "extension order", "disputed assessment" ] }, { "id": "fil-q-time-3", "kind": "lifecycle", "text": "Which response obligation is said to arise from this filing or service and how is its trigger kept conditional until evidenced?", "answer_data": [ "response obligation reference", "trigger condition", "responsible participant", "conditional deadline", "review status" ] } ], "data_elements": [ { "id": "fil-de-time-1", "name": "trigger evidence", "description": "Candidate answer group: trigger evidence; time-computation rule; legal timezone; holiday calendar version; due-time assertion. Preserve unknown, disputed and not-applicable states with source and observer; nested instance schema remains a profile task.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] }, { "id": "fil-de-time-2", "name": "assessment actor", "description": "Candidate answer group: assessment actor; selected filing event; precision; outage evidence; extension order; disputed assessment. Preserve unknown, disputed and not-applicable states with source and observer; nested instance schema remains a profile task.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] }, { "id": "fil-de-time-3", "name": "response obligation reference", "description": "Candidate answer group: response obligation reference; trigger condition; responsible participant; conditional deadline; review status. Preserve unknown, disputed and not-applicable states with source and observer; nested instance schema remains a profile task.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] } ], "artifacts": [ { "id": "fil-art-time", "name": "Time assertion and review record", "description": "Proposed governed evidence record for deadline and legal-time assessment. It may be a reference or structured record, not necessarily a separate file.", "media_or_form": [ "Structured record or reference to controlled document" ], "serial": true, "identity_strategy": "Authoritative master-system artifact ID and namespace first; otherwise governed IRI, then local UUID or ULID. Preserve revision and rendition identities; dates and digests alone are not identity.", "source_refs": [ "SRC-001", "SRC-005" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "fil-b-continuity", "name": "Service and document continuity", "description": "Record delivery evidence and authorized changes to the document.", "rationale": "Service may precede filing and each amended document needs its own authority and revision links.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-008" ], "layers": [ { "id": "fil-l-service", "name": "Recipient-specific service evidence context", "description": "Questions and evidence for recipient-specific service evidence, limited to this filing document.", "source_refs": [ "SRC-005", "SRC-007" ], "findings": [ { "id": "fil-f-service", "name": "Recipient-specific service evidence", "description": "Record the legal service regime and recipient-specific observations; initial process and later service differ. Delivery acknowledgements, deemed service and legal sufficiency must not be conflated.", "source_refs": [ "SRC-005", "SRC-007" ], "questions": [ { "id": "fil-q-service-1", "kind": "access", "text": "Which recipients and permitted intermediaries must receive which revision or authorized rendition under the selected service rule?", "answer_data": [ "recipient reference", "intermediary capacity", "service address version", "rendition", "service obligation or exception" ] }, { "id": "fil-q-service-2", "kind": "evidence", "text": "Which method, dispatch, delivery, deemed-service assertion and certificate support service for each recipient?", "answer_data": [ "service method", "dispatch time", "delivery evidence", "deemed-time rule", "certificate reference", "dispute status" ] }, { "id": "fil-q-service-3", "kind": "exception", "text": "What failed delivery, alternative-service order, dispensation or foreign-service requirement remains for authorized review?", "answer_data": [ "failure event", "alternative-method authority", "dispensation evidence", "foreign destination", "unresolved review" ] } ], "data_elements": [ { "id": "fil-de-service-1", "name": "recipient reference", "description": "Candidate answer group: recipient reference; intermediary capacity; service address version; rendition; service obligation or exception. Preserve unknown, disputed and not-applicable states with source and observer; nested instance schema remains a profile task.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-007" ] }, { "id": "fil-de-service-2", "name": "service method", "description": "Candidate answer group: service method; dispatch time; delivery evidence; deemed-time rule; certificate reference; dispute status. Preserve unknown, disputed and not-applicable states with source and observer; nested instance schema remains a profile task.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-007" ] }, { "id": "fil-de-service-3", "name": "failure event", "description": "Candidate answer group: failure event; alternative-method authority; dispensation evidence; foreign destination; unresolved review. Preserve unknown, disputed and not-applicable states with source and observer; nested instance schema remains a profile task.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-007" ] } ], "artifacts": [ { "id": "fil-art-service", "name": "Recipient service evidence register", "description": "Proposed governed evidence record for recipient-specific service evidence. It may be a reference or structured record, not necessarily a separate file.", "media_or_form": [ "Structured record or reference to controlled document" ], "serial": true, "identity_strategy": "Authoritative master-system artifact ID and namespace first; otherwise governed IRI, then local UUID or ULID. Preserve revision and rendition identities; dates and digests alone are not identity.", "source_refs": [ "SRC-005", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "fil-l-revision", "name": "Amendment and supersession authority context", "description": "Questions and evidence for amendment and supersession authority, limited to this filing document.", "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ], "findings": [ { "id": "fil-f-revision", "name": "Amendment and supersession authority", "description": "Proposed revision lineage preserves submitted bytes while linking later amendments, corrections or withdrawal assertions to their authority. A local update or withdrawal flag cannot remove a filing from a court record.", "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ], "questions": [ { "id": "fil-q-revision-1", "kind": "authority", "text": "What consent, rule entitlement or court permission supports the proposed amendment for this procedural stage?", "answer_data": [ "amendment basis", "consent reference", "permission order", "service stage", "scope of authority" ] }, { "id": "fil-q-revision-2", "kind": "lifecycle", "text": "Which revision supersedes or supplements which earlier document and what approval and service consequences remain unresolved?", "answer_data": [ "prior revision", "new revision", "relation type", "authority reference", "renewed verification and service requirements" ] }, { "id": "fil-q-revision-3", "kind": "state", "text": "What authoritative notice or order supports a withdrawal, striking or correction status while retaining the historical record?", "answer_data": [ "status assertion", "notice or order reference", "effective date assertion", "affected scope", "historical rendition reference" ] } ], "data_elements": [ { "id": "fil-de-revision-1", "name": "amendment basis", "description": "Candidate answer group: amendment basis; consent reference; permission order; service stage; scope of authority. Preserve unknown, disputed and not-applicable states with source and observer; nested instance schema remains a profile task.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ] }, { "id": "fil-de-revision-2", "name": "prior revision", "description": "Candidate answer group: prior revision; new revision; relation type; authority reference; renewed verification and service requirements. Preserve unknown, disputed and not-applicable states with source and observer; nested instance schema remains a profile task.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ] }, { "id": "fil-de-revision-3", "name": "status assertion", "description": "Candidate answer group: status assertion; notice or order reference; effective date assertion; affected scope; historical rendition reference. Preserve unknown, disputed and not-applicable states with source and observer; nested instance schema remains a profile task.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ] } ], "artifacts": [ { "id": "fil-art-revision", "name": "Revision and disposition lineage", "description": "Proposed governed evidence record for amendment and supersession authority. It may be a reference or structured record, not necessarily a separate file.", "media_or_form": [ "Structured record or reference to controlled document" ], "serial": true, "identity_strategy": "Authoritative master-system artifact ID and namespace first; otherwise governed IRI, then local UUID or ULID. Preserve revision and rendition identities; dates and digests alone are not identity.", "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "fil-b-governance", "name": "Access, provenance and retention", "description": "Control disclosure and accountable local record maintenance.", "rationale": "Public metadata, confidential payload and preservation obligations need independent treatment.", "source_refs": [ "SRC-001", "SRC-006", "SRC-008" ], "layers": [ { "id": "fil-l-disclosure", "name": "Protected and public renditions context", "description": "Questions and evidence for protected and public renditions, limited to this filing document.", "source_refs": [ "SRC-001", "SRC-006" ], "findings": [ { "id": "fil-f-disclosure", "name": "Protected and public renditions", "description": "Access is evaluated per recipient and artifact, including attachments and restricted identifiers. A public docket entry is not a blanket release of all content.", "source_refs": [ "SRC-001", "SRC-006" ], "questions": [ { "id": "fil-q-disclosure-1", "kind": "privacy", "text": "Which identifiers or passages require protection and what rule or order supports each redaction or sealing decision?", "answer_data": [ "protected field or passage", "legal basis", "seal order", "authorized redaction", "review date" ] }, { "id": "fil-q-disclosure-2", "kind": "access", "text": "Which requester may see which rendition and attachments, with what permission, purpose and recorded decision?", "answer_data": [ "requester capacity", "authorized rendition", "attachment scope", "permission basis", "access decision" ] }, { "id": "fil-q-disclosure-3", "kind": "security", "text": "How is a mistaken disclosure contained and referred for correction without pretending local suppression recalls external copies?", "answer_data": [ "disclosure incident reference", "affected copies", "containment action", "responsible officer", "unresolved dissemination" ] } ], "data_elements": [ { "id": "fil-de-disclosure-1", "name": "protected field or passage", "description": "Candidate answer group: protected field or passage; legal basis; seal order; authorized redaction; review date. Preserve unknown, disputed and not-applicable states with source and observer; nested instance schema remains a profile task.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-006" ] }, { "id": "fil-de-disclosure-2", "name": "requester capacity", "description": "Candidate answer group: requester capacity; authorized rendition; attachment scope; permission basis; access decision. Preserve unknown, disputed and not-applicable states with source and observer; nested instance schema remains a profile task.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-006" ] }, { "id": "fil-de-disclosure-3", "name": "disclosure incident reference", "description": "Candidate answer group: disclosure incident reference; affected copies; containment action; responsible officer; unresolved dissemination. Preserve unknown, disputed and not-applicable states with source and observer; nested instance schema remains a profile task.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-006" ] } ], "artifacts": [ { "id": "fil-art-disclosure", "name": "Access and rendition decision record", "description": "Proposed governed evidence record for protected and public renditions. It may be a reference or structured record, not necessarily a separate file.", "media_or_form": [ "Structured record or reference to controlled document" ], "serial": true, "identity_strategy": "Authoritative master-system artifact ID and namespace first; otherwise governed IRI, then local UUID or ULID. Preserve revision and rendition identities; dates and digests alone are not identity.", "source_refs": [ "SRC-001", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "fil-l-provenance", "name": "Provenance and record disposition context", "description": "Questions and evidence for provenance and record disposition, limited to this filing document.", "source_refs": [ "SRC-008", "SRC-006" ], "findings": [ { "id": "fil-f-provenance", "name": "Provenance and record disposition", "description": "Proposed governance records assertion origin, transformations and controlled disposition. Retention duration and erasure authority are unresolved local-policy inputs; provenance vocabularies supply no retention mandate.", "source_refs": [ "SRC-008", "SRC-006" ], "questions": [ { "id": "fil-q-provenance-1", "kind": "provenance", "text": "Who supplied or changed each material assertion, from which source revision and at what event and observation times?", "answer_data": [ "assertion reference", "actor", "source revision", "event time", "observation time", "confidence or dispute" ] }, { "id": "fil-q-provenance-2", "kind": "retention", "text": "Which approved schedule, legal hold and payload scope govern retention or disposal of each local copy and its logs?", "answer_data": [ "schedule authority", "hold reference", "copy scope", "disposition date", "minimal tombstone policy" ] }, { "id": "fil-q-provenance-3", "kind": "interoperability", "text": "What mapping and loss report accompanies export so that identity, restrictions and disputed status survive exchange?", "answer_data": [ "mapping version", "source and target IDs", "restriction transfer", "loss report", "export review" ] } ], "data_elements": [ { "id": "fil-de-provenance-1", "name": "assertion reference", "description": "Candidate answer group: assertion reference; actor; source revision; event time; observation time; confidence or dispute. Preserve unknown, disputed and not-applicable states with source and observer; nested instance schema remains a profile task.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-008", "SRC-006" ] }, { "id": "fil-de-provenance-2", "name": "schedule authority", "description": "Candidate answer group: schedule authority; hold reference; copy scope; disposition date; minimal tombstone policy. Preserve unknown, disputed and not-applicable states with source and observer; nested instance schema remains a profile task.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-008", "SRC-006" ] }, { "id": "fil-de-provenance-3", "name": "mapping version", "description": "Candidate answer group: mapping version; source and target IDs; restriction transfer; loss report; export review. Preserve unknown, disputed and not-applicable states with source and observer; nested instance schema remains a profile task.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-008", "SRC-006" ] } ], "artifacts": [ { "id": "fil-art-provenance", "name": "Provenance and disposition policy record", "description": "Proposed governed evidence record for provenance and record disposition. It may be a reference or structured record, not necessarily a separate file.", "media_or_form": [ "Structured record or reference to controlled document" ], "serial": true, "identity_strategy": "Authoritative master-system artifact ID and namespace first; otherwise governed IRI, then local UUID or ULID. Preserve revision and rendition identities; dates and digests alone are not identity.", "source_refs": [ "SRC-008", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "fil-fn-register", "name": "Register document identity", "description": "Proposed, unimplemented local operation. Create or reconcile a local record without declaring that filing occurred.", "inputs": [ "Document key or provisional key", "Parent or intended case reference", "Identity evidence" ], "outputs": [ "Local record revision or refusal", "Alias reconciliation result" ], "preconditions": [ "Authorized local role, permitted purpose and expected revision are supplied.", "Custodian and namespace are identified; ambiguous matches remain unresolved." ], "effects": [ "Append identity and typed aliases; retain pending case assignment.", "Return an explicit refusal with reason when authority, evidence or required profile is missing. No external legal action is performed." ], "source_refs": [ "SRC-007", "SRC-008" ] }, { "id": "fil-fn-review", "name": "Record readiness review", "description": "Proposed, unimplemented local operation. Attach a human or profile check result, retaining failures and unknowns.", "inputs": [ "Exact document revision", "Pinned criteria", "Reviewer evidence" ], "outputs": [ "Readiness record or refusal" ], "preconditions": [ "Authorized local role, permitted purpose and expected revision are supplied.", "Reviewer is authorized for the stated criteria; no inferred legal sufficiency." ], "effects": [ "Append check outcomes without filing, signing or paying fees.", "Return an explicit refusal with reason when authority, evidence or required profile is missing. No external legal action is performed." ], "source_refs": [ "SRC-001", "SRC-006", "SRC-007" ] }, { "id": "fil-fn-status", "name": "Reconcile submission evidence", "description": "Proposed, unimplemented local operation. Link observed responses to their document and transaction without inventing a legal filing event.", "inputs": [ "Receipt or court response", "Transaction and document references", "Observation time" ], "outputs": [ "Correlated status assertions or refusal" ], "preconditions": [ "Authorized local role, permitted purpose and expected revision are supplied.", "Response provenance is retained; duplicate and conflicting responses can be represented." ], "effects": [ "Append per-document receipt, review or docket assertions; do not overwrite a contrary assertion.", "Return an explicit refusal with reason when authority, evidence or required profile is missing. No external legal action is performed." ], "source_refs": [ "SRC-007", "SRC-008" ] }, { "id": "fil-fn-deadline", "name": "Record reviewed time assertion", "description": "Proposed, unimplemented local operation. Store a supplied deadline assessment with its rule, trigger and review state.", "inputs": [ "Due-time assertion", "Rule and calendar versions", "Trigger evidence", "Reviewer" ], "outputs": [ "Qualified time assessment or refusal" ], "preconditions": [ "Authorized local role, permitted purpose and expected revision are supplied.", "Legal profile and reviewer are supplied; calculations are not implemented by this operation." ], "effects": [ "Record conditional or disputed assessment without starting a legal timer or certifying timeliness.", "Return an explicit refusal with reason when authority, evidence or required profile is missing. No external legal action is performed." ], "source_refs": [ "SRC-001", "SRC-005" ] }, { "id": "fil-fn-service", "name": "Record service evidence", "description": "Proposed, unimplemented local operation. Index a service assertion per recipient and exact revision.", "inputs": [ "Recipient and method", "Certificate or delivery evidence", "Rule or order reference" ], "outputs": [ "Recipient evidence entry or refusal" ], "preconditions": [ "Authorized local role, permitted purpose and expected revision are supplied.", "Recipient scope and evidence access are permitted; missing legal effect remains unknown." ], "effects": [ "Append evidence without sending a document or declaring legally sufficient service.", "Return an explicit refusal with reason when authority, evidence or required profile is missing. No external legal action is performed." ], "source_refs": [ "SRC-005", "SRC-007" ] }, { "id": "fil-fn-revision", "name": "Link authorized revision", "description": "Proposed, unimplemented local operation. Connect a proposed or evidenced amendment while preserving historical rendition identity.", "inputs": [ "Old and new revision", "Authority evidence", "Change reason" ], "outputs": [ "Revision relation or refusal" ], "preconditions": [ "Authorized local role, permitted purpose and expected revision are supplied.", "Existing bytes are not overwritten; permission scope is reviewed by a competent role." ], "effects": [ "Append a revision or supersession link; renewed verification or service remains separately tracked.", "Return an explicit refusal with reason when authority, evidence or required profile is missing. No external legal action is performed." ], "source_refs": [ "SRC-003", "SRC-004", "SRC-008" ] }, { "id": "fil-fn-view", "name": "Prepare authorized local view", "description": "Proposed, unimplemented local operation. Derive an access-controlled view from an approved redaction instruction.", "inputs": [ "Requester scope", "Approved redaction and seal rules", "Source rendition" ], "outputs": [ "Controlled view with provenance or refusal" ], "preconditions": [ "Authorized local role, permitted purpose and expected revision are supplied.", "Disclosure authority and current orders are resolved for all included attachments." ], "effects": [ "Create local derived rendition and record the decision; export requires separate authority.", "Return an explicit refusal with reason when authority, evidence or required profile is missing. No external legal action is performed." ], "source_refs": [ "SRC-001", "SRC-006", "SRC-008" ] } ], "composition": [ { "target": "WM-POL-009", "relation": "REFERENCE", "required": false, "purpose": "Back-reference to the containing court case under the incoming candidate CONTAINS relation. Parent identity can be pending for an originating document; case lifecycle stays outside this model. Pin neighbor version before integration.", "source_refs": [ "SRC-001", "SRC-007" ] }, { "target": "Electronic filing transaction master", "relation": "REFERENCE", "required": false, "purpose": "Typed transaction and message correlation; one transaction may include multiple document entities. Binding is proposed, not a registered runtime dependency.", "source_refs": [ "SRC-007" ] }, { "target": "Party, representation and court authority masters", "relation": "REFERENCE", "required": false, "purpose": "Resolve identities and authority evidence externally; this model records document-specific capacity assertions only. No executable neighbor binding is claimed.", "source_refs": [ "SRC-001", "SRC-003" ] }, { "target": "Evidence exhibit and judicial order masters", "relation": "REFERENCE", "required": false, "purpose": "Preserve independently mastered evidence and orders. Attachment or citation does not transfer lifecycle ownership or prove a proposition.", "source_refs": [ "SRC-001", "SRC-006" ] }, { "target": "Electronic Court Filing 5.0 CS01", "relation": "ALIGN", "required": false, "purpose": "Conceptual mapping of document, message, transaction and review status; no conformance claim or automatic filing interface.", "source_refs": [ "SRC-007" ] }, { "target": "PROV-O 2013-04-30", "relation": "ALIGN", "required": false, "purpose": "Conceptual attribution, derivation and revision relationships; no truth or legal-authority certification.", "source_refs": [ "SRC-008" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Named accountable document custodian and competent court-record authority, scoped by copy and role", "Pinned procedural profile and approved authority, access and escalation rules", "Master namespaces, legal retention schedule, holds and source provenance" ], "namespace_guidance": "Use opaque document IDs qualified by master namespace. Keep case, transaction, message, document and rendition keys typed; retain aliases and provisional reconciliation state.", "registry_links": [ "vr.wm-pol-019", "WM-POL-009 incoming containment candidate; resolve and pin before runtime integration" ] }, "canon_and_patch": { "canonicalization_rules": [ "Preserve source assertions and original bytes; normalize only typed references with matching evidence.", "No receipt, signature, docket number, silence or content digest proves legal validity or merits." ], "patch_rules": [ "Require actor, purpose, evidence, expected revision and idempotency key for local append or correction.", "Preserve revision lineage without imposing perpetual personal payload retention; authorized disposal must be explicit." ], "compatibility_rules": [ "Version legal profiles and exchange mappings; reject or flag loss of authority, access, time precision, document identity or dispute qualifiers." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier with namespace and revision", "Governed stable global identifier or IRI with version", "Adopting Dimension UUID or ULID with reconciliation status" ], "timestamp_rule": "Use RFC 3339 with seconds and explicit offset or Z for instants. Distinguish dispatch, receipt, review, docketing, asserted legal effect and observation or ingestion time. Preserve legal timezone, date-only values, precision and unknowns; never invent midnight.", "serial_naming_rule": "Opaque document key plus artifact role and immutable revision or sequence; no personal data or date-only identity in filenames.", "integrity_rule": "Retain algorithm, digest, signer evidence and transformation provenance when available; a digest checks bytes, not truth, legal filing, service or authority." }, "policies": [ "This single-provider reviewable draft has no independent external review and cannot claim canonical completeness.", "The civil examples are jurisdiction-limited; applying a deadline, service rule, permission or legal consequence requires a qualified current profile.", "Proposed local operations do not sign, file, serve, pay fees, choose legal strategy or determine merits.", "Access and retention are adopting-Dimension governance requirements, not universal law derived from a provenance standard. Dangerous subject content is limited to policy-level references." ], "crud": { "read": [ "Authorize recipient, purpose, revision and rendition including each attachment; retain source and disputed-status qualifiers." ], "create": [ "Require custodian, master or provisional identity, intended forum and source evidence; do not require an assigned case number for a draft originating document." ], "update": [ "Append authorized revisions and evidence with concurrency checks; never overwrite submitted bytes to simulate a lawful amendment." ], "delete": [ "Apply the approved retention schedule, legal holds and lawful erasure rules to payloads, replicas and logs; no universal retention duration is supplied.", "Disposition execution belongs to the adopting Dimension records authority. Record a minimal lawful tombstone where permitted; deleting a local copy neither withdraws a filing nor erases the court master." ] }, "roles": [ { "name": "Document custodian", "responsibilities": [ "Maintain local identity, revisions and references within assigned copy scope." ] }, { "name": "Filing party or authorized representative", "responsibilities": [ "Supply content and capacity evidence; authorize legally consequential action outside these local operations." ] }, { "name": "Procedural legal reviewer", "responsibilities": [ "Resolve applicable rules, exceptions, time assertions and amendment authority." ] }, { "name": "Court records liaison", "responsibilities": [ "Reconcile authoritative document numbers and status responses without deciding merits." ] }, { "name": "Access and records officer", "responsibilities": [ "Approve disclosure, redaction, retention, holds and disposition policy." ] } ], "access": { "default_rule": "Deny content access unless recipient, purpose, scope and current restrictions permit it; public docket metadata alone grants no payload access.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Specific rule or court order may permit access, restrict it or require a different rendition; record authority and scope rather than a blanket override.", "Self-represented participants are evaluated under the applicable profile, not excluded by role naming." ], "audit_requirements": [ "Record reads, local changes, view derivation and exports with actor, scope, revision, purpose and result; minimize retained personal data under the approved schedule." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "AGENTS.md and owner authority/access policies", "spec.yaml and all publication holds", "Pinned procedural profile, court orders and authorized source renditions" ] } }, "coverage": { "claim": "Source-grounded proposed structure for one legal filing or pleading document entity, using selected US federal and England and Wales civil examples plus ECF and PROV-O. A separate frozen local no-tools self-audit found no critical conflicts. Independent review, source/version, legal-profile and executable-conformance holds remain; this is a reviewable draft, not a universal legal workflow.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Typed master, provisional, alias and rendition identifiers." }, { "dimension": "lifecycle", "status": "covered", "notes": "Drafts, submissions, service, amendment and disposition assertions are separate." }, { "dimension": "relationships", "status": "covered", "notes": "Case containment is incoming; external transaction, parties, evidence and orders remain separate." }, { "dimension": "temporal", "status": "covered", "notes": "Rule, trigger, legal timezone, calendar and reviewed time assertions." }, { "dimension": "provenance", "status": "covered", "notes": "Attribution, original rendition and transformation history." }, { "dimension": "ownership", "status": "covered", "notes": "Role-based document custodian and competent authority; no commercial owner assignment." }, { "dimension": "validation", "status": "gap", "notes": "Research-schema validation is distinct from instance schemas and legal sufficiency." }, { "dimension": "access", "status": "covered", "notes": "Recipient and artifact scope, restrictions and redaction authority." }, { "dimension": "retention and deletion", "status": "gap", "notes": "Policy questions and execution owner provided; no jurisdictional schedule or duration verified." }, { "dimension": "interoperability", "status": "gap", "notes": "ECF and PROV-O conceptual alignments; mappings and fixtures not implemented." }, { "dimension": "direct properties", "status": "covered", "notes": "Class, language, status, dates and claimed amounts; no physical mass or dimensions of an abstract filing." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Caption, master references, controlled bytes and source responses are recognition evidence, not automatic proof." }, { "dimension": "capabilities and hazards", "status": "covered", "notes": "Seven proposed local operations; false acceptance, missed time limits, fabricated citations and disclosure remain hazards." }, { "dimension": "context and evidence", "status": "covered", "notes": "Profile and source-bound observations retain disputes and unknowns." } ], "known_omissions": [ "Independent external review is waived; local self-audit is not a second-provider opinion.", "Direct HTTP checks are not performed because the sandbox blocks them; browser content was available but current-law and source-version verification remain incomplete.", "Nested answer schemas, executable deadline calculations, exchange mappings, neighbor pins and adversarial instance fixtures are not implemented.", "Criminal, family, appellate, administrative tribunal, arbitration and international service profiles require separate research. No convention-specific workflow is admitted from the supplement.", "Local rules, practice directions, signing technology, fee schedules, accessibility details, record-retention law and licensing need adoption review." ], "conflicts": [], "regional_assumptions": [ "US federal civil rules and England and Wales civil rules are distinct examples, not rules for Cyprus or every court or tribunal.", "ECF 5.0 CS01 is an exchange specification, not an authority to file, serve or decide legal effects." ], "adversarial_checks": [ "Reject equating all filed papers with pleadings or all filing records with electronic transactions.", "Reject a required pre-existing case number, a universal lawyer-only filer or a contested-proceeding invariant.", "Reject receipt as acceptance, acceptance as service, requested relief as an award, or an allegation as truth.", "Reject unrestricted attachment disclosure from public docket visibility.", "Reject silent replacement of submitted bytes or an unreviewed local edit as permission to amend." ] }, "researchAdjudication": { "providerMode": "single-provider-waiver", "activeProviders": [ "codex" ], "waivedProviders": [ "claude", "grok" ], "providerPolicy": { "contract_version": "1.0.0", "mode": "single-provider-waiver", "effective_at": "2026-09-06T00:00:00Z", "scope": "Canonical single-stream subject-model research after the six-workstream consolidation", "active_providers": [ "codex" ], "waived_providers": [ { "provider": "claude", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "Claude produced no result on prior 1800-second and 900-second attempts and again timed out on bounded 600-second Sonnet and 300-second Haiku passes. The owner prioritized completion over provider availability." }, { "provider": "grok", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "The repository owner authorized completion without Grok when Grok is unavailable, slow or schema-invalid. Grok may still be attempted as a bounded supplemental reviewer, but its failure never blocks a valid Claude plus no-tools result." } ], "review_rule": "Codex may complete source-grounded fallback research after bounded Claude and Grok attempts fail. It requires a separate no-tools adversarial audit and remains reviewable-draft with a visible absence-of-external-review hold.", "supplemental_provider_attempts": [ { "provider": "claude", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." }, { "provider": "grok", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." } ] }, "boundaryDecision": { "entry_kind": "entity", "status": "accepted", "rationale": "The root is a persistent procedural document record across preparation, submission evidence and linked revisions. Filing events, multi-document transactions and the containing case remain separate. The registry standalone-mm label describes the catalogue record plane and is not the subject-kind enum." }, "decisions": [ { "concept": "Document versus filing transaction", "disposition": "accepted with explicit boundary", "rationale": "Document identity is the root, while transaction and message identifiers are typed references. Multiple documents in one transaction and repeated submissions remain representable." }, { "concept": "Pleading terminology", "disposition": "qualified", "rationale": "Classification asks for the governing profile and explicitly distinguishes pleadings, motions and other papers. The title does not make every filing a pleading." }, { "concept": "Incoming case containment", "disposition": "accepted", "rationale": "WM-POL-009 remains the case master. A pending parent number for an originating document does not transfer case lifecycle ownership or require a fabricated court identifier." }, { "concept": "Supplement assumptions", "disposition": "partly rejected", "rationale": "The result rejects contested status, professional representation and absence of all properties as invariants. It admits supported leads only after official-source review; no legacy specification is registered." }, { "concept": "Signature and factual truth", "disposition": "separated", "rationale": "Filer and signer capacity, verification defects and attributed positions remain distinct. Signed verification and citation existence are not treated as proof of truth or admissibility." }, { "concept": "Receipt, review, docketing and legal effect", "disposition": "separated", "rationale": "Per-document observations preserve conflicts and partial responses. Readiness approval or an exchange acknowledgement cannot establish legal acceptance, service, timeliness or merits." }, { "concept": "Time calculation", "disposition": "accepted as assertion recording only", "rationale": "Questions require trigger, rule, calendar, timezone and reviewer. The function records a supplied assessment and explicitly does not implement a legal deadline engine." }, { "concept": "Recipient service and foreign profiles", "disposition": "qualified and deferred", "rationale": "Recipients, renditions, methods, proof and deemed effects remain separate. Initial process and subsequent service differ, and international service implementation is visibly deferred." }, { "concept": "Amendment and document history", "disposition": "accepted", "rationale": "Revision links require authority evidence and preserve submitted renditions. Local changes or withdrawal flags do not grant amendment permission or remove court records." }, { "concept": "Access and retention", "disposition": "accepted as governed design", "rationale": "Artifact-specific disclosure and explicit disposal authority reconcile lineage with lawful payload retention limits. Public metadata grants no blanket attachment access; no retention duration is asserted." }, { "concept": "Local operation powers", "disposition": "accepted as proposed only", "rationale": "All seven operations require local authority, revision and evidence, have refusal results and explicitly exclude external legal action. The draft does not implement signing, filing, service, fees or merits decisions." }, { "concept": "Executable schemas and mappings", "disposition": "deferred", "rationale": "Candidate optional answer objects and conceptual ECF and PROV-O alignments are research structure. Nested schemas, pinned neighbors, mapping tests and adversarial instance fixtures are still needed." }, { "concept": "Source verification and independent review", "disposition": "limited and held", "rationale": "Eight browser-readable sources from four organizations support selected concepts. Direct HTTP checks were not attempted in the blocked sandbox, and a local no-tools self-audit is not an independent provider opinion." } ], "publicationHolds": [ "Independent external review is absent under the owner-authorized single-provider waiver. Claude and Grok were skipped with zero attempts; this separate local Codex self-audit is not a second-provider review.", "Live source and version verification is incomplete. All eight sources yielded browser text for selected review, but direct HTTP requests were not attempted because the sandbox blocks them: zero attempts and zero measured HTTP 200 responses, not eight failed requests. The coordinator must run check_sources.py outside the sandbox and verify versions and claim support.", "Jurisdiction-specific legal applicability, local rules, effective dates, exceptions, signing, service, deadlines, fees, retention, translations and licensing require qualified profile review. US federal and England and Wales civil examples are not universal or Cyprus-specific rules.", "Nested instance schemas, required-field profiles, pinned neighbor bindings, executable ECF and PROV-O mappings and adversarial instance fixtures are incomplete. Seven local operations are proposed and unimplemented; no runtime, exchange-conformance or legal-compliance certification is claimed.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Verify exact source URLs, response integrity, effective legal versions, exception coverage and profile applicability; do not close the gate from HTTP success alone.", "Define and test document, rendition and transaction schemas with originating documents, mixed transaction outcomes, conflicting receipts, failed service, disputed time, authorized amendment and restricted attachments.", "Research additional proceeding types, international service, accessibility, local fee and retention rules before adopting those profiles.", "Restore independent external review before any canonical or publishable-draft promotion." ] }, "statistics": { "sources": 8, "bundles": 6, "layers": 12, "findings": 12, "questions": 36, "artifacts": 12, "functions": 7 } }