# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-10-06T14:30:55Z", "synthesisSha256": "e05997e19d9f5160ec2cb1b10917bfb07c8e358a113f179d85dce348247e627f", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-COM-001", "registryId": "vr.wm-com-001", "name": "Communications Service", "version": "0.3.0", "previousVersions": [], "entryKind": "entity", "family": "World Models", "category": "Information and virtual systems", "industry": [ "Cross-industry" ], "domain": [ "INF.COM.SVC" ], "tags": [ "communications", "service", "inf.com.svc" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-com-001-communications-service/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-com-001", "model": { "registry_id": "vr.wm-com-001", "model_id": "WM-COM-001", "name": "Communications Service", "entry_kind": "entity", "purpose": "Describe a persistent communications service provision and the scoped evidence supporting its dependencies, capability and assurance.", "scope_statement": "One operator-scoped persistent service record. Service-owned assertions refer to separately mastered resources, parties, infrastructure, commitments and observations. Proposed research structure, not an operational telecom controller.", "in_scope": [ "Identity, roles, lifecycle and service-facing connectivity.", "Coverage, authority dependencies, objectives and aggregate assurance evidence.", "Provenance, controlled disclosure and record continuity." ], "out_of_scope": [ "Physical infrastructure, spectrum allocation masters, address/number registries and routing control.", "Messages, subscriber dossiers, billing ledgers, active measurement and legal determinations." ], "boundary_notes": [ { "neighbor": "WM-ORG-001", "distinction": "Candidate binding for operator, customer and regulator parties; no party master is copied.", "source_refs": [ "SRC-001" ] }, { "neighbor": "WM-SFT-018", "distinction": "Candidate service demarcation and logical endpoint binding; endpoint ownership remains external.", "source_refs": [ "SRC-002" ] }, { "neighbor": "WM-BLT-003", "distinction": "Candidate infrastructure-network realization reference; service identity is not cable identity.", "source_refs": [ "SRC-001", "SRC-002" ] }, { "neighbor": "WM-SFT-016", "distinction": "Candidate versioned commitment reference; legal agreement and remedies remain external.", "source_refs": [ "SRC-002", "SRC-008" ] }, { "neighbor": "WM-SFT-017", "distinction": "Candidate observation reference for quality and operational evidence.", "source_refs": [ "SRC-003", "SRC-008" ] }, { "neighbor": "WM-XCT-001", "distinction": "Candidate stewardship and authority reference; no universal commons ownership is asserted.", "source_refs": [ "SRC-006" ] }, { "neighbor": "WM-XCT-035", "distinction": "Candidate retention-policy binding; adopting policy must specify applicable copy-level rules.", "source_refs": [ "SRC-003", "SRC-007" ] }, { "neighbor": "WM-ACT-027", "distinction": "Optional interaction evidence reference; message content and sessions retain separate masters.", "source_refs": [ "SRC-001" ] }, { "neighbor": "RFC 9083", "distinction": "Conceptual RDAP projection only; no executable conformance mapping is supplied.", "source_refs": [ "SRC-009" ] }, { "neighbor": "Legacy F9", "distinction": "Reconcile the legacy multi-object domain into a service entity with external dependencies. Reject automatic grant reversion, universal public lookup and inherited conformance claims.", "source_refs": [ "SRC-001", "SRC-006", "SRC-009" ] } ] }, "sources": [ { "id": "SRC-001", "title": "Service Models Explained", "organization": "IETF", "url": "https://www.rfc-editor.org/rfc/rfc8309.html", "version_or_date": "RFC 8309, January 2018", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:29:49Z", "relevance": "Sections 2, 3, 5 and 9: customer-facing service requirements differ from realization and operational state." }, { "id": "SRC-002", "title": "A Framework for Network Slices in Networks Built from IETF Technologies", "organization": "IETF", "url": "https://www.rfc-editor.org/rfc/rfc9543.html", "version_or_date": "RFC 9543, March 2024", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:29:49Z", "relevance": "Sections 3.2, 4.2 and 5: service demarcation, connectivity and objectives; slice-specific example, not a universal telecom schema." }, { "id": "SRC-003", "title": "Specification of the IP Flow Information Export Protocol for the Exchange of Flow Information", "organization": "IETF", "url": "https://www.rfc-editor.org/rfc/rfc7011.html", "version_or_date": "RFC 7011, September 2013", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:29:49Z", "relevance": "Sections 2, 3.1 and 11.8: scoped observations, export loss and privacy-sensitive flow information." }, { "id": "SRC-004", "title": "Number Resources", "organization": "IANA", "url": "https://www.iana.org/numbers", "version_or_date": "Undated live registry landing page, accessed 2026-10-06", "source_type": "registry", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:29:49Z", "relevance": "Registry and regional allocation links identify external number-resource authorities; no individual allocation was checked." }, { "id": "SRC-005", "title": "The international public telecommunication numbering plan", "organization": "ITU", "url": "https://www.itu.int/rec/T-REC-E.164", "version_or_date": "Catalogue lists E.164 (02/2026); full text not reviewed", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:29:49Z", "relevance": "Catalogue establishes numbering-plan reference and edition; no national assignment, portability rule or subscriber identity is certified." }, { "id": "SRC-006", "title": "Radio Regulations", "organization": "ITU", "url": "https://www.itu.int/pub/R-REG-RR", "version_or_date": "2024 edition catalogue; national implementation unverified", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:29:49Z", "relevance": "Catalogue establishes the international regulatory reference; grant conditions require the actual national authority record." }, { "id": "SRC-007", "title": "PROV-O: The PROV Ontology", "organization": "W3C", "url": "https://www.w3.org/TR/prov-o/", "version_or_date": "W3C Recommendation, 30 April 2013", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:29:49Z", "relevance": "Section 3 and derivation/revision properties support evidence lineage; provenance does not certify correctness." }, { "id": "SRC-008", "title": "User related QoS parameter definitions and measurements; Part 4: Internet access", "organization": "ETSI", "url": "https://www.etsi.org/deliver/etsi_EG/202000_202099/20205704/01.02.01_60/eg_20205704v010201p.pdf", "version_or_date": "EG 202 057-4 V1.2.1, July 2008; historical measurement guide", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:29:49Z", "relevance": "Clauses 4.3 and 4.4: distinguish test conditions, traffic monitoring, representativeness and collection periods; current conformance not claimed." }, { "id": "SRC-009", "title": "JSON Responses for the Registration Data Access Protocol (RDAP)", "organization": "IETF", "url": "https://www.rfc-editor.org/rfc/rfc9083.html", "version_or_date": "RFC 9083, June 2021", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:29:49Z", "relevance": "Sections 4, 5.4 and 5.5: registry-scoped handles, IP network and autonomous-system registration records." }, { "id": "SRC-010", "title": "BGP Prefix Origin Validation", "organization": "IETF", "url": "https://www.rfc-editor.org/rfc/rfc6811.html", "version_or_date": "RFC 6811, January 2013; base semantics only, update chain unverified", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T14:29:49Z", "relevance": "Sections 1-3: route origin evidence and cache-dependent validation; complete path attestation is outside its scope." } ], "structure": { "bundles": [ { "id": "service-record", "name": "Service identity", "description": "Proposed local grouping for service identity of a communications service.", "rationale": "Keep service-owned assertions together while external records retain their own authoritative masters.", "source_refs": [ "SRC-001", "SRC-007" ], "layers": [ { "id": "layer-identity", "name": "Service identity and classification", "description": "Identify one persistent provision of communications capability. Catalogue offerings, customer agreements and individual sessions are external references. Identity survives a change of access technology only when the authoritative master records continuity.", "source_refs": [ "SRC-001" ], "findings": [ { "id": "finding-identity", "name": "Service identity and classification", "description": "Identify one persistent provision of communications capability. Catalogue offerings, customer agreements and individual sessions are external references. Identity survives a change of access technology only when the authoritative master records continuity.", "source_refs": [ "SRC-001" ], "questions": [ { "id": "finding-identity-q1", "text": "Which master-system service identifier and namespace distinguish this provision from its offering and subscription?", "kind": "identity", "answer_data": [ "serviceKey" ] }, { "id": "finding-identity-q2", "text": "Which communications capability and service profile classify this provision?", "kind": "classification", "answer_data": [ "serviceClass" ] }, { "id": "finding-identity-q3", "text": "Which operator role stewards this record and which separate party records identify provider and customer?", "kind": "ownership", "answer_data": [ "partyRoles" ] } ], "data_elements": [ { "id": "finding-identity-data1", "name": "serviceKey", "description": "Candidate structured answer to: Which master-system service identifier and namespace distinguish this provision from its offering and subscription? Profile must define nested fields, null reasons and validation before operational use.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001" ] }, { "id": "finding-identity-data2", "name": "serviceClass", "description": "Candidate structured answer to: Which communications capability and service profile classify this provision? Profile must define nested fields, null reasons and validation before operational use.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001" ] }, { "id": "finding-identity-data3", "name": "partyRoles", "description": "Candidate structured answer to: Which operator role stewards this record and which separate party records identify provider and customer? Profile must define nested fields, null reasons and validation before operational use.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001" ] } ], "artifacts": [ { "id": "finding-identity-artifact", "name": "Service identity and classification evidence record", "description": "Versioned evidence reference or access-controlled local projection; raw subscriber payload is excluded.", "media_or_form": [ "application/json", "evidence reference" ], "serial": true, "identity_strategy": "Authoritative master-system record identifier first; otherwise source namespace and native identifier; otherwise locally assigned opaque identifier. Revisions are separate from stable identity; content digest is integrity metadata.", "source_refs": [ "SRC-001" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-lifecycle", "name": "Lifecycle and realization evidence", "description": "Keep requested, administratively enabled, observed operational and retired states separate. A local revision records evidence and effective time; it does not provision or terminate a network service.", "source_refs": [ "SRC-001", "SRC-007" ], "findings": [ { "id": "finding-lifecycle", "name": "Lifecycle and realization evidence", "description": "Keep requested, administratively enabled, observed operational and retired states separate. A local revision records evidence and effective time; it does not provision or terminate a network service.", "source_refs": [ "SRC-001", "SRC-007" ], "questions": [ { "id": "finding-lifecycle-q1", "text": "Which state transition is proposed and which evidence supports its effective interval?", "kind": "lifecycle", "answer_data": [ "transition" ] }, { "id": "finding-lifecycle-q2", "text": "What operational state is observed, by whom, and how old is that observation?", "kind": "state", "answer_data": [ "observedState" ] }, { "id": "finding-lifecycle-q3", "text": "How are failed activation, partial suspension and disputed termination recorded without replacing earlier evidence?", "kind": "exception", "answer_data": [ "exceptions" ] } ], "data_elements": [ { "id": "finding-lifecycle-data1", "name": "transition", "description": "Candidate structured answer to: Which state transition is proposed and which evidence supports its effective interval? Profile must define nested fields, null reasons and validation before operational use.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] }, { "id": "finding-lifecycle-data2", "name": "observedState", "description": "Candidate structured answer to: What operational state is observed, by whom, and how old is that observation? Profile must define nested fields, null reasons and validation before operational use.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] }, { "id": "finding-lifecycle-data3", "name": "exceptions", "description": "Candidate structured answer to: How are failed activation, partial suspension and disputed termination recorded without replacing earlier evidence? Profile must define nested fields, null reasons and validation before operational use.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] } ], "artifacts": [ { "id": "finding-lifecycle-artifact", "name": "Lifecycle and realization evidence evidence record", "description": "Versioned evidence reference or access-controlled local projection; raw subscriber payload is excluded.", "media_or_form": [ "application/json", "evidence reference" ], "serial": true, "identity_strategy": "Authoritative master-system record identifier first; otherwise source namespace and native identifier; otherwise locally assigned opaque identifier. Revisions are separate from stable identity; content digest is integrity metadata.", "source_refs": [ "SRC-001", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "delivery-scope", "name": "Delivery scope", "description": "Proposed local grouping for delivery scope of a communications service.", "rationale": "Keep service-owned assertions together while external records retain their own authoritative masters.", "source_refs": [ "SRC-002", "SRC-008" ], "layers": [ { "id": "layer-connectivity", "name": "Demarcation and dependencies", "description": "Describe service-facing attachment points and directed connectivity separately from underlay equipment. Reference interconnection, transit or peer dependencies with responsibility boundaries; internal topology need not be disclosed.", "source_refs": [ "SRC-002" ], "findings": [ { "id": "finding-connectivity", "name": "Demarcation and dependencies", "description": "Describe service-facing attachment points and directed connectivity separately from underlay equipment. Reference interconnection, transit or peer dependencies with responsibility boundaries; internal topology need not be disclosed.", "source_refs": [ "SRC-002" ], "questions": [ { "id": "finding-connectivity-q1", "text": "Which demarcation points and directed connectivity groups belong to this service profile?", "kind": "composition", "answer_data": [ "connectivity" ] }, { "id": "finding-connectivity-q2", "text": "Which network and interconnection references support delivery and where does responsibility change?", "kind": "relationship", "answer_data": [ "dependencies" ] }, { "id": "finding-connectivity-q3", "text": "Which attachment or traffic-profile exclusions limit the stated delivery commitment?", "kind": "constraint", "answer_data": [ "exclusions" ] } ], "data_elements": [ { "id": "finding-connectivity-data1", "name": "connectivity", "description": "Candidate structured answer to: Which demarcation points and directed connectivity groups belong to this service profile? Profile must define nested fields, null reasons and validation before operational use.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002" ] }, { "id": "finding-connectivity-data2", "name": "dependencies", "description": "Candidate structured answer to: Which network and interconnection references support delivery and where does responsibility change? Profile must define nested fields, null reasons and validation before operational use.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002" ] }, { "id": "finding-connectivity-data3", "name": "exclusions", "description": "Candidate structured answer to: Which attachment or traffic-profile exclusions limit the stated delivery commitment? Profile must define nested fields, null reasons and validation before operational use.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002" ] } ], "artifacts": [ { "id": "finding-connectivity-artifact", "name": "Demarcation and dependencies evidence record", "description": "Versioned evidence reference or access-controlled local projection; raw subscriber payload is excluded.", "media_or_form": [ "application/json", "evidence reference" ], "serial": true, "identity_strategy": "Authoritative master-system record identifier first; otherwise source namespace and native identifier; otherwise locally assigned opaque identifier. Revisions are separate from stable identity; content digest is integrity metadata.", "source_refs": [ "SRC-002" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-coverage", "name": "Coverage claims and evidence", "description": "Proposed evidence discipline: store coverage claims with area, method, time, uncertainty and limitations. Predicted availability, observed performance and eligibility to order are separate assertions; measurements at selected locations do not prove universal coverage.", "source_refs": [ "SRC-008" ], "findings": [ { "id": "finding-coverage", "name": "Coverage claims and evidence", "description": "Proposed evidence discipline: store coverage claims with area, method, time, uncertainty and limitations. Predicted availability, observed performance and eligibility to order are separate assertions; measurements at selected locations do not prove universal coverage.", "source_refs": [ "SRC-008" ], "questions": [ { "id": "finding-coverage-q1", "text": "Which area, site set or access locations does this coverage assertion concern?", "kind": "spatial", "answer_data": [ "coverageScope" ] }, { "id": "finding-coverage-q2", "text": "Was coverage predicted, measured or declared, under what conditions and with what uncertainty?", "kind": "measurement", "answer_data": [ "coverageMethod" ] }, { "id": "finding-coverage-q3", "text": "Which gaps, stale samples or exclusions prevent this coverage assertion from proving availability at a requested location?", "kind": "quality", "answer_data": [ "coverageLimits" ] } ], "data_elements": [ { "id": "finding-coverage-data1", "name": "coverageScope", "description": "Candidate structured answer to: Which area, site set or access locations does this coverage assertion concern? Profile must define nested fields, null reasons and validation before operational use.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-008" ] }, { "id": "finding-coverage-data2", "name": "coverageMethod", "description": "Candidate structured answer to: Was coverage predicted, measured or declared, under what conditions and with what uncertainty? Profile must define nested fields, null reasons and validation before operational use.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-008" ] }, { "id": "finding-coverage-data3", "name": "coverageLimits", "description": "Candidate structured answer to: Which gaps, stale samples or exclusions prevent this coverage assertion from proving availability at a requested location? Profile must define nested fields, null reasons and validation before operational use.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-008" ] } ], "artifacts": [ { "id": "finding-coverage-artifact", "name": "Coverage claims and evidence evidence record", "description": "Versioned evidence reference or access-controlled local projection; raw subscriber payload is excluded.", "media_or_form": [ "application/json", "evidence reference" ], "serial": true, "identity_strategy": "Authoritative master-system record identifier first; otherwise source namespace and native identifier; otherwise locally assigned opaque identifier. Revisions are separate from stable identity; content digest is integrity metadata.", "source_refs": [ "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "resource-authority", "name": "Resource authority", "description": "Proposed local grouping for resource authority of a communications service.", "rationale": "Keep service-owned assertions together while external records retain their own authoritative masters.", "source_refs": [ "SRC-006", "SRC-005" ], "layers": [ { "id": "layer-spectrum", "name": "Spectrum dependency and authority", "description": "Record optional references to applicable band plans and competent-authority permissions. Wireless authorization is profile-dependent. A licence expiry cannot be interpreted here as automatic return of a band, deletion of a service or permission to transmit.", "source_refs": [ "SRC-006" ], "findings": [ { "id": "finding-spectrum", "name": "Spectrum dependency and authority", "description": "Record optional references to applicable band plans and competent-authority permissions. Wireless authorization is profile-dependent. A licence expiry cannot be interpreted here as automatic return of a band, deletion of a service or permission to transmit.", "source_refs": [ "SRC-006" ], "questions": [ { "id": "finding-spectrum-q1", "text": "Which competent authority record or exemption basis governs this service spectrum dependency?", "kind": "authority", "answer_data": [ "authorityBasis" ] }, { "id": "finding-spectrum-q2", "text": "For which territory and effective interval is the referenced permission asserted to apply?", "kind": "temporal", "answer_data": [ "permissionScope" ] }, { "id": "finding-spectrum-q3", "text": "Which unresolved conditions or national-profile reviews block reliance on the spectrum reference?", "kind": "requirement", "answer_data": [ "authorityHolds" ] } ], "data_elements": [ { "id": "finding-spectrum-data1", "name": "authorityBasis", "description": "Candidate structured answer to: Which competent authority record or exemption basis governs this service spectrum dependency? Profile must define nested fields, null reasons and validation before operational use.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-006" ] }, { "id": "finding-spectrum-data2", "name": "permissionScope", "description": "Candidate structured answer to: For which territory and effective interval is the referenced permission asserted to apply? Profile must define nested fields, null reasons and validation before operational use.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-006" ] }, { "id": "finding-spectrum-data3", "name": "authorityHolds", "description": "Candidate structured answer to: Which unresolved conditions or national-profile reviews block reliance on the spectrum reference? Profile must define nested fields, null reasons and validation before operational use.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-006" ] } ], "artifacts": [ { "id": "finding-spectrum-artifact", "name": "Spectrum dependency and authority evidence record", "description": "Versioned evidence reference or access-controlled local projection; raw subscriber payload is excluded.", "media_or_form": [ "application/json", "evidence reference" ], "serial": true, "identity_strategy": "Authoritative master-system record identifier first; otherwise source namespace and native identifier; otherwise locally assigned opaque identifier. Revisions are separate from stable identity; content digest is integrity metadata.", "source_refs": [ "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-numbering", "name": "Numbering-plan and assignment references", "description": "Link number resources only for services that use them. Keep the numbering plan, assignment evidence and any portability evidence distinct. A number is not the stable identity of the service or its subscriber.", "source_refs": [ "SRC-005" ], "findings": [ { "id": "finding-numbering", "name": "Numbering-plan and assignment references", "description": "Link number resources only for services that use them. Keep the numbering plan, assignment evidence and any portability evidence distinct. A number is not the stable identity of the service or its subscriber.", "source_refs": [ "SRC-005" ], "questions": [ { "id": "finding-numbering-q1", "text": "Which numbering plan, resource identifier and issuing authority qualify this number reference?", "kind": "identity", "answer_data": [ "numberReference" ] }, { "id": "finding-numbering-q2", "text": "Which dated assignment or portability evidence supports the current association with the service?", "kind": "provenance", "answer_data": [ "assignmentEvidence" ] }, { "id": "finding-numbering-q3", "text": "How are number reuse, disputed assignment or a service without telephone numbering represented?", "kind": "exception", "answer_data": [ "numberExceptions" ] } ], "data_elements": [ { "id": "finding-numbering-data1", "name": "numberReference", "description": "Candidate structured answer to: Which numbering plan, resource identifier and issuing authority qualify this number reference? Profile must define nested fields, null reasons and validation before operational use.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-005" ] }, { "id": "finding-numbering-data2", "name": "assignmentEvidence", "description": "Candidate structured answer to: Which dated assignment or portability evidence supports the current association with the service? Profile must define nested fields, null reasons and validation before operational use.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-005" ] }, { "id": "finding-numbering-data3", "name": "numberExceptions", "description": "Candidate structured answer to: How are number reuse, disputed assignment or a service without telephone numbering represented? Profile must define nested fields, null reasons and validation before operational use.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-005" ] } ], "artifacts": [ { "id": "finding-numbering-artifact", "name": "Numbering-plan and assignment references evidence record", "description": "Versioned evidence reference or access-controlled local projection; raw subscriber payload is excluded.", "media_or_form": [ "application/json", "evidence reference" ], "serial": true, "identity_strategy": "Authoritative master-system record identifier first; otherwise source namespace and native identifier; otherwise locally assigned opaque identifier. Revisions are separate from stable identity; content digest is integrity metadata.", "source_refs": [ "SRC-005" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "internet-resources", "name": "Internet resource dependencies", "description": "Proposed local grouping for internet resource dependencies of a communications service.", "rationale": "Keep service-owned assertions together while external records retain their own authoritative masters.", "source_refs": [ "SRC-004", "SRC-009", "SRC-010" ], "layers": [ { "id": "layer-registration", "name": "Address and autonomous-system registration", "description": "Keep registry authority and handles with address or autonomous-system references. Registration evidence is separate from endpoint assignment and observed use. A public registry link does not make its contacts or local service associations public.", "source_refs": [ "SRC-004", "SRC-009" ], "findings": [ { "id": "finding-registration", "name": "Address and autonomous-system registration", "description": "Keep registry authority and handles with address or autonomous-system references. Registration evidence is separate from endpoint assignment and observed use. A public registry link does not make its contacts or local service associations public.", "source_refs": [ "SRC-004", "SRC-009" ], "questions": [ { "id": "finding-registration-q1", "text": "Which registry authority and handle identify the IP network or autonomous-system resource?", "kind": "identity", "answer_data": [ "registrationKey" ] }, { "id": "finding-registration-q2", "text": "Which effective-dated association connects this registered resource to the service?", "kind": "relationship", "answer_data": [ "resourceBinding" ] }, { "id": "finding-registration-q3", "text": "Which RDAP response version, retrieval time and unresolved or redacted fields must the mapping preserve?", "kind": "interoperability", "answer_data": [ "rdapEvidence" ] } ], "data_elements": [ { "id": "finding-registration-data1", "name": "registrationKey", "description": "Candidate structured answer to: Which registry authority and handle identify the IP network or autonomous-system resource? Profile must define nested fields, null reasons and validation before operational use.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-009" ] }, { "id": "finding-registration-data2", "name": "resourceBinding", "description": "Candidate structured answer to: Which effective-dated association connects this registered resource to the service? Profile must define nested fields, null reasons and validation before operational use.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-009" ] }, { "id": "finding-registration-data3", "name": "rdapEvidence", "description": "Candidate structured answer to: Which RDAP response version, retrieval time and unresolved or redacted fields must the mapping preserve? Profile must define nested fields, null reasons and validation before operational use.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-009" ] } ], "artifacts": [ { "id": "finding-registration-artifact", "name": "Address and autonomous-system registration evidence record", "description": "Versioned evidence reference or access-controlled local projection; raw subscriber payload is excluded.", "media_or_form": [ "application/json", "evidence reference" ], "serial": true, "identity_strategy": "Authoritative master-system record identifier first; otherwise source namespace and native identifier; otherwise locally assigned opaque identifier. Revisions are separate from stable identity; content digest is integrity metadata.", "source_refs": [ "SRC-004", "SRC-009" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-routing", "name": "Route observation and origin evidence", "description": "Reference observed announcements and origin-validation results separately from registration. Preserve observer, prefix, origin, cache time and result semantics. Origin validation does not prove end-to-end path safety, reachability or permission for local route changes.", "source_refs": [ "SRC-010" ], "findings": [ { "id": "finding-routing", "name": "Route observation and origin evidence", "description": "Reference observed announcements and origin-validation results separately from registration. Preserve observer, prefix, origin, cache time and result semantics. Origin validation does not prove end-to-end path safety, reachability or permission for local route changes.", "source_refs": [ "SRC-010" ], "questions": [ { "id": "finding-routing-q1", "text": "Which observation identifies the announced prefix and origin at a stated time?", "kind": "evidence", "answer_data": [ "routeObservation" ] }, { "id": "finding-routing-q2", "text": "Which validation profile and cache snapshot support the reported origin result, including unknown or unavailable evidence?", "kind": "validation", "answer_data": [ "originEvidence" ] }, { "id": "finding-routing-q3", "text": "Which limits prevent interpreting this origin result as path validation or service reachability?", "kind": "security", "answer_data": [ "originLimits" ] } ], "data_elements": [ { "id": "finding-routing-data1", "name": "routeObservation", "description": "Candidate structured answer to: Which observation identifies the announced prefix and origin at a stated time? Profile must define nested fields, null reasons and validation before operational use.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-010" ] }, { "id": "finding-routing-data2", "name": "originEvidence", "description": "Candidate structured answer to: Which validation profile and cache snapshot support the reported origin result, including unknown or unavailable evidence? Profile must define nested fields, null reasons and validation before operational use.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-010" ] }, { "id": "finding-routing-data3", "name": "originLimits", "description": "Candidate structured answer to: Which limits prevent interpreting this origin result as path validation or service reachability? Profile must define nested fields, null reasons and validation before operational use.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-010" ] } ], "artifacts": [ { "id": "finding-routing-artifact", "name": "Route observation and origin evidence evidence record", "description": "Versioned evidence reference or access-controlled local projection; raw subscriber payload is excluded.", "media_or_form": [ "application/json", "evidence reference" ], "serial": true, "identity_strategy": "Authoritative master-system record identifier first; otherwise source namespace and native identifier; otherwise locally assigned opaque identifier. Revisions are separate from stable identity; content digest is integrity metadata.", "source_refs": [ "SRC-010" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "service-assurance", "name": "Service assurance", "description": "Proposed local grouping for service assurance of a communications service.", "rationale": "Keep service-owned assertions together while external records retain their own authoritative masters.", "source_refs": [ "SRC-002", "SRC-008", "SRC-003" ], "layers": [ { "id": "layer-objectives", "name": "Commitments and measured quality", "description": "Reference versioned objectives separately from observed quality. State metric, direction, units, interval and applicable exclusions. A profile decides how evidence is evaluated; insufficient evidence remains unknown rather than pass.", "source_refs": [ "SRC-002", "SRC-008" ], "findings": [ { "id": "finding-objectives", "name": "Commitments and measured quality", "description": "Reference versioned objectives separately from observed quality. State metric, direction, units, interval and applicable exclusions. A profile decides how evidence is evaluated; insufficient evidence remains unknown rather than pass.", "source_refs": [ "SRC-002", "SRC-008" ], "questions": [ { "id": "finding-objectives-q1", "text": "Which objective revision, metric, unit, direction and scope define the service commitment?", "kind": "requirement", "answer_data": [ "objectiveRef" ] }, { "id": "finding-objectives-q2", "text": "Which method, equipment, sampling interval and uncertainty qualify the observed quality?", "kind": "measurement", "answer_data": [ "qualityEvidence" ] }, { "id": "finding-objectives-q3", "text": "Which profile evaluation records met, unmet or insufficient evidence without converting a target into a measurement?", "kind": "decision", "answer_data": [ "evaluation" ] } ], "data_elements": [ { "id": "finding-objectives-data1", "name": "objectiveRef", "description": "Candidate structured answer to: Which objective revision, metric, unit, direction and scope define the service commitment? Profile must define nested fields, null reasons and validation before operational use.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-008" ] }, { "id": "finding-objectives-data2", "name": "qualityEvidence", "description": "Candidate structured answer to: Which method, equipment, sampling interval and uncertainty qualify the observed quality? Profile must define nested fields, null reasons and validation before operational use.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-008" ] }, { "id": "finding-objectives-data3", "name": "evaluation", "description": "Candidate structured answer to: Which profile evaluation records met, unmet or insufficient evidence without converting a target into a measurement? Profile must define nested fields, null reasons and validation before operational use.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-008" ] } ], "artifacts": [ { "id": "finding-objectives-artifact", "name": "Commitments and measured quality evidence record", "description": "Versioned evidence reference or access-controlled local projection; raw subscriber payload is excluded.", "media_or_form": [ "application/json", "evidence reference" ], "serial": true, "identity_strategy": "Authoritative master-system record identifier first; otherwise source namespace and native identifier; otherwise locally assigned opaque identifier. Revisions are separate from stable identity; content digest is integrity metadata.", "source_refs": [ "SRC-002", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-traffic", "name": "Traffic aggregates and observation scope", "description": "Attach traffic summaries with observation scope, period, direction, unit and derivation. Preserve loss and sampling limitations. Aggregation must avoid overlapping counters and cannot be treated as billing evidence without a separate accepted profile.", "source_refs": [ "SRC-003" ], "findings": [ { "id": "finding-traffic", "name": "Traffic aggregates and observation scope", "description": "Attach traffic summaries with observation scope, period, direction, unit and derivation. Preserve loss and sampling limitations. Aggregation must avoid overlapping counters and cannot be treated as billing evidence without a separate accepted profile.", "source_refs": [ "SRC-003" ], "questions": [ { "id": "finding-traffic-q1", "text": "Which exporter, observation domain, period, direction and unit delimit the traffic summary?", "kind": "measurement", "answer_data": [ "trafficScope" ] }, { "id": "finding-traffic-q2", "text": "Which sampling, lost records, resets or overlapping observation points affect this aggregate?", "kind": "quality", "answer_data": [ "trafficLimits" ] }, { "id": "finding-traffic-q3", "text": "Which input references and transformation revision allow this aggregate to be traced without embedding raw flows?", "kind": "provenance", "answer_data": [ "trafficLineage" ] } ], "data_elements": [ { "id": "finding-traffic-data1", "name": "trafficScope", "description": "Candidate structured answer to: Which exporter, observation domain, period, direction and unit delimit the traffic summary? Profile must define nested fields, null reasons and validation before operational use.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003" ] }, { "id": "finding-traffic-data2", "name": "trafficLimits", "description": "Candidate structured answer to: Which sampling, lost records, resets or overlapping observation points affect this aggregate? Profile must define nested fields, null reasons and validation before operational use.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003" ] }, { "id": "finding-traffic-data3", "name": "trafficLineage", "description": "Candidate structured answer to: Which input references and transformation revision allow this aggregate to be traced without embedding raw flows? Profile must define nested fields, null reasons and validation before operational use.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003" ] } ], "artifacts": [ { "id": "finding-traffic-artifact", "name": "Traffic aggregates and observation scope evidence record", "description": "Versioned evidence reference or access-controlled local projection; raw subscriber payload is excluded.", "media_or_form": [ "application/json", "evidence reference" ], "serial": true, "identity_strategy": "Authoritative master-system record identifier first; otherwise source namespace and native identifier; otherwise locally assigned opaque identifier. Revisions are separate from stable identity; content digest is integrity metadata.", "source_refs": [ "SRC-003" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "record-governance", "name": "Record governance", "description": "Proposed local grouping for record governance of a communications service.", "rationale": "Keep service-owned assertions together while external records retain their own authoritative masters.", "source_refs": [ "SRC-007", "SRC-003" ], "layers": [ { "id": "layer-evidence", "name": "Evidence revisions and service incidents", "description": "Proposed local record policy: attach scoped incident and restoration assertions with provenance. Preserve contradictory observations and distinguish revision from service identity. An artifact hash detects byte changes, not truth, legal authority or authenticity by itself.", "source_refs": [ "SRC-007" ], "findings": [ { "id": "finding-evidence", "name": "Evidence revisions and service incidents", "description": "Proposed local record policy: attach scoped incident and restoration assertions with provenance. Preserve contradictory observations and distinguish revision from service identity. An artifact hash detects byte changes, not truth, legal authority or authenticity by itself.", "source_refs": [ "SRC-007" ], "questions": [ { "id": "finding-evidence-q1", "text": "Which incident or restoration assertion affects which part of the service and during what interval?", "kind": "event", "answer_data": [ "incidentRef" ] }, { "id": "finding-evidence-q2", "text": "Which agent, activity and source revisions support the assurance record?", "kind": "provenance", "answer_data": [ "evidenceChain" ] }, { "id": "finding-evidence-q3", "text": "Which contradictory, stale or unavailable evidence prevents accepting the proposed record revision?", "kind": "validation", "answer_data": [ "revisionChecks" ] } ], "data_elements": [ { "id": "finding-evidence-data1", "name": "incidentRef", "description": "Candidate structured answer to: Which incident or restoration assertion affects which part of the service and during what interval? Profile must define nested fields, null reasons and validation before operational use.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-007" ] }, { "id": "finding-evidence-data2", "name": "evidenceChain", "description": "Candidate structured answer to: Which agent, activity and source revisions support the assurance record? Profile must define nested fields, null reasons and validation before operational use.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-007" ] }, { "id": "finding-evidence-data3", "name": "revisionChecks", "description": "Candidate structured answer to: Which contradictory, stale or unavailable evidence prevents accepting the proposed record revision? Profile must define nested fields, null reasons and validation before operational use.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-007" ] } ], "artifacts": [ { "id": "finding-evidence-artifact", "name": "Evidence revisions and service incidents evidence record", "description": "Versioned evidence reference or access-controlled local projection; raw subscriber payload is excluded.", "media_or_form": [ "application/json", "evidence reference" ], "serial": true, "identity_strategy": "Authoritative master-system record identifier first; otherwise source namespace and native identifier; otherwise locally assigned opaque identifier. Revisions are separate from stable identity; content digest is integrity metadata.", "source_refs": [ "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-disclosure", "name": "Disclosure, retention and disposal", "description": "Proposed local policy requires purpose-bound access and profile-defined retention. Aggregate traffic can still reveal people or confidential operations. Release only reviewed projections; disposal records distinguish payload erasure, remaining lawful evidence and external copies.", "source_refs": [ "SRC-003", "SRC-007" ], "findings": [ { "id": "finding-disclosure", "name": "Disclosure, retention and disposal", "description": "Proposed local policy requires purpose-bound access and profile-defined retention. Aggregate traffic can still reveal people or confidential operations. Release only reviewed projections; disposal records distinguish payload erasure, remaining lawful evidence and external copies.", "source_refs": [ "SRC-003", "SRC-007" ], "questions": [ { "id": "finding-disclosure-q1", "text": "Which role, purpose and artifact-level scope authorize access to this service evidence?", "kind": "access", "answer_data": [ "accessDecision" ] }, { "id": "finding-disclosure-q2", "text": "Which suppression or disclosure review prevents re-identification and exposure of sensitive operations in an aggregate?", "kind": "privacy", "answer_data": [ "releaseReview" ] }, { "id": "finding-disclosure-q3", "text": "Which retention trigger, hold and disposal evidence govern each copy without silently promising external erasure?", "kind": "retention", "answer_data": [ "disposition" ] } ], "data_elements": [ { "id": "finding-disclosure-data1", "name": "accessDecision", "description": "Candidate structured answer to: Which role, purpose and artifact-level scope authorize access to this service evidence? Profile must define nested fields, null reasons and validation before operational use.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-007" ] }, { "id": "finding-disclosure-data2", "name": "releaseReview", "description": "Candidate structured answer to: Which suppression or disclosure review prevents re-identification and exposure of sensitive operations in an aggregate? Profile must define nested fields, null reasons and validation before operational use.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-007" ] }, { "id": "finding-disclosure-data3", "name": "disposition", "description": "Candidate structured answer to: Which retention trigger, hold and disposal evidence govern each copy without silently promising external erasure? Profile must define nested fields, null reasons and validation before operational use.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-007" ] } ], "artifacts": [ { "id": "finding-disclosure-artifact", "name": "Disclosure, retention and disposal evidence record", "description": "Versioned evidence reference or access-controlled local projection; raw subscriber payload is excluded.", "media_or_form": [ "application/json", "evidence reference" ], "serial": true, "identity_strategy": "Authoritative master-system record identifier first; otherwise source namespace and native identifier; otherwise locally assigned opaque identifier. Revisions are separate from stable identity; content digest is integrity metadata.", "source_refs": [ "SRC-003", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "register-service", "name": "Register a local service record", "description": "Proposed, unimplemented local operation. Record master identity, service class and party-role references.", "inputs": [ "master identifier", "profile revision", "authorized party references" ], "outputs": [ "new record revision or refusal" ], "preconditions": [ "Authorized steward role and purpose at the affected scopes.", "Expected current revision matches; references and evidence are resolvable or explicitly unknown.", "Applicable profile and retention/access rules are supplied; otherwise refuse with reasons." ], "effects": [ "Create a local record only; no network provisioning." ], "source_refs": [ "SRC-001" ] }, { "id": "revise-binding", "name": "Revise a service dependency", "description": "Proposed, unimplemented local operation. Record effective-dated endpoint, resource or interconnection references.", "inputs": [ "service revision", "dependency references", "effective interval" ], "outputs": [ "validated binding revision or unresolved-reference report" ], "preconditions": [ "Authorized steward role and purpose at the affected scopes.", "Expected current revision matches; references and evidence are resolvable or explicitly unknown.", "Applicable profile and retention/access rules are supplied; otherwise refuse with reasons." ], "effects": [ "Append the binding revision; do not allocate numbers, spectrum or routes." ], "source_refs": [ "SRC-002", "SRC-009" ] }, { "id": "attach-observation", "name": "Attach an assurance observation", "description": "Proposed, unimplemented local operation. Record quality, coverage, traffic or incident evidence with scoped provenance.", "inputs": [ "service revision", "observation scope and time", "method and source reference" ], "outputs": [ "evidence link or rejection with reason" ], "preconditions": [ "Authorized steward role and purpose at the affected scopes.", "Expected current revision matches; references and evidence are resolvable or explicitly unknown.", "Applicable profile and retention/access rules are supplied; otherwise refuse with reasons." ], "effects": [ "Store an authorized evidence projection; no active network probe or raw-flow collection." ], "source_refs": [ "SRC-003", "SRC-008" ] }, { "id": "evaluate-evidence", "name": "Evaluate evidence sufficiency", "description": "Proposed, unimplemented local operation. Assess a proposed local assertion against an explicitly supplied profile.", "inputs": [ "assertion revision", "profile and objective revisions", "evidence set" ], "outputs": [ "met, unmet or insufficient-evidence assessment with reasons" ], "preconditions": [ "Authorized steward role and purpose at the affected scopes.", "Expected current revision matches; references and evidence are resolvable or explicitly unknown.", "Applicable profile and retention/access rules are supplied; otherwise refuse with reasons." ], "effects": [ "Append a local assessment; no SLA settlement or service-state change." ], "source_refs": [ "SRC-002", "SRC-007" ] }, { "id": "prepare-projection", "name": "Prepare a restricted projection", "description": "Proposed, unimplemented local operation. Build a local preview under an approved disclosure profile.", "inputs": [ "authorized purpose", "recipient role", "release profile", "source revisions" ], "outputs": [ "redacted preview or denial report" ], "preconditions": [ "Authorized steward role and purpose at the affected scopes.", "Expected current revision matches; references and evidence are resolvable or explicitly unknown.", "Applicable profile and retention/access rules are supplied; otherwise refuse with reasons." ], "effects": [ "Write a local preview only; no delivery, publication or access expansion." ], "source_refs": [ "SRC-003", "SRC-007" ] }, { "id": "record-retirement", "name": "Record retirement or disposal evidence", "description": "Proposed, unimplemented local operation. Record a supported retirement assertion and separate copy-specific disposal outcomes.", "inputs": [ "service revision", "authority evidence", "retention schedule and holds", "copy inventory" ], "outputs": [ "retirement revision or blocked disposition report" ], "preconditions": [ "Authorized steward role and purpose at the affected scopes.", "Expected current revision matches; references and evidence are resolvable or explicitly unknown.", "Applicable profile and retention/access rules are supplied; otherwise refuse with reasons." ], "effects": [ "Append local evidence; do not terminate connectivity, erase external copies or release regulated resources." ], "source_refs": [ "SRC-001", "SRC-007" ] } ], "composition": [ { "target": "WM-ORG-001", "relation": "REFERENCE", "purpose": "Candidate binding for operator, customer and regulator parties; no party master is copied.", "required": false, "source_refs": [ "SRC-001" ] }, { "target": "WM-SFT-018", "relation": "REFERENCE", "purpose": "Candidate service demarcation and logical endpoint binding; endpoint ownership remains external.", "required": false, "source_refs": [ "SRC-002" ] }, { "target": "WM-BLT-003", "relation": "REFERENCE", "purpose": "Candidate infrastructure-network realization reference; service identity is not cable identity.", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "WM-SFT-016", "relation": "REFERENCE", "purpose": "Candidate versioned commitment reference; legal agreement and remedies remain external.", "required": false, "source_refs": [ "SRC-002", "SRC-008" ] }, { "target": "WM-SFT-017", "relation": "REFERENCE", "purpose": "Candidate observation reference for quality and operational evidence.", "required": false, "source_refs": [ "SRC-003", "SRC-008" ] }, { "target": "WM-XCT-001", "relation": "REFERENCE", "purpose": "Candidate stewardship and authority reference; no universal commons ownership is asserted.", "required": false, "source_refs": [ "SRC-006" ] }, { "target": "WM-XCT-035", "relation": "REFERENCE", "purpose": "Candidate retention-policy binding; adopting policy must specify applicable copy-level rules.", "required": false, "source_refs": [ "SRC-003", "SRC-007" ] }, { "target": "WM-ACT-027", "relation": "REFERENCE", "purpose": "Optional interaction evidence reference; message content and sessions retain separate masters.", "required": false, "source_refs": [ "SRC-001" ] }, { "target": "RFC 9083", "relation": "ALIGN", "purpose": "Conceptual RDAP projection only; no executable conformance mapping is supplied.", "required": false, "source_refs": [ "SRC-009" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Declare an accountable service-record steward role and escalation contact; no brand owner is prescribed.", "Declare authoritative service master, namespace, identity continuity policy and profile revision.", "Declare purpose, jurisdiction, evidence access, retention and dependency-resolution policy." ], "namespace_guidance": "Use an owner-controlled namespace and stable opaque local identifiers; keep source namespace with imported keys and never use a mutable phone number as the service key.", "registry_links": [ "vr.wm-com-001", "Candidate neighbors must be pinned to reviewed versions before implementation." ] }, "canon_and_patch": { "canonicalization_rules": [ "This research package is noncanonical and reviewable-draft; keep all source and provider holds visible.", "Preserve source values, units and raw time precision with normalized representations; unknown differs from false and zero." ], "patch_rules": [ "Use expected-revision checks and append a reasoned change record with actor, evidence and effective time.", "A dependency replacement does not silently transfer service identity or alter the external master." ], "compatibility_rules": [ "Breaking identity, metric, authority or scope semantics require a new profile version and explicit migration.", "Historical mappings are evidence; no legacy conformance label or wildcard import is inherited." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier with issuer namespace.", "Native source identifier with source authority.", "Locally assigned opaque identifier when neither exists." ], "timestamp_rule": "Use RFC 3339 timestamps with seconds and explicit UTC offset; preserve original precision and distinguish observation, effective and ingestion time.", "serial_naming_rule": "Use stable evidence key plus separate revision sequence; dates and filenames never replace identity.", "integrity_rule": "Record content digest, source and retrieval evidence for retained payloads; a digest is not a signature or truth certificate. Respect disposal rules for sensitive payloads." }, "policies": [ "Proposed local governance rules require adopter review; citations support concepts, not universal legal compliance.", "Default to minimal service metadata and aggregate evidence; no message contents, credentials or raw subscriber flows.", "Spectrum, numbering, emergency-access, lawful-access and retention obligations require competent profile review; no automated legal inference.", "No local operation may change routing, transmit, allocate resources, collect live traffic or broaden access." ], "crud": { "read": [ "Resolve the applicable role, purpose, scope and redaction policy before reading evidence." ], "create": [ "Check master identity, duplicate risk, source attribution and authorized scope before creating a local service assertion." ], "update": [ "Require current revision and record corrections without overwriting source evidence; preserve contradictions and time scopes." ], "delete": [ "Retire references rather than silently reassigning identities. Apply copy-specific retention and lawful holds; erase payload only under authorized policy and keep a minimal lawful tombstone where permitted.", "Do not interpret local deletion as termination, resource release or erasure of external copies." ] }, "roles": [ { "name": "Service steward", "responsibilities": [ "Maintains service identity and approved local revisions." ] }, { "name": "Evidence custodian", "responsibilities": [ "Maintains provenance, integrity and copy-specific retention." ] }, { "name": "Assurance reviewer", "responsibilities": [ "Checks objective scope, measurement limitations and contradictory evidence." ] }, { "name": "Access reviewer", "responsibilities": [ "Approves purpose-limited projections and examines disclosure risk." ] }, { "name": "Domain authority reviewer", "responsibilities": [ "Resolves spectrum, numbering and jurisdictional authority questions without granting rights through this model." ] } ], "access": { "default_rule": "Deny by default; authorize role and purpose at bundle, layer, finding and artifact scopes. A public standard or registry URL never grants access to local service data.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "A public projection requires explicit release review, suppression rules and minimal fields.", "Urgent access requires a documented applicable policy, bounded scope and retrospective review; no universal exception is assumed." ], "audit_requirements": [ "Record access decision, actor role, purpose, affected identifiers, time, policy revision and outcome without copying sensitive payload into the audit log." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Read AGENTS.md and reviewable-draft holds.", "Read spec.yaml, adopting owner policy and pinned neighbor profiles.", "Resolve source evidence and scope before preparing any local revision." ] } }, "coverage": { "claim": "Source-grounded proposed structure for one persistent communications service provision, with scoped resource references and assurance evidence. A separate local no-tools self-audit found no critical contradiction. Independent review, source/version verification, adopting profiles and executable conformance remain holds. This reviewable draft is neither exhaustive nor canonical.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Service key differs from offering, number and endpoint." }, { "dimension": "lifecycle", "status": "covered", "notes": "Requested, administrative and observed states remain separate." }, { "dimension": "relationships", "status": "covered", "notes": "Candidate external masters are referenced, not embedded as owned entities." }, { "dimension": "temporal", "status": "covered", "notes": "Effective, observed and recorded times remain distinct." }, { "dimension": "provenance", "status": "covered", "notes": "Lineage and contrary evidence are retained under retention policy." }, { "dimension": "ownership", "status": "covered", "notes": "Generic steward roles do not imply spectrum ownership." }, { "dimension": "validation", "status": "gap", "notes": "Structural validation only; executable instance validation remains a gap." }, { "dimension": "access", "status": "covered", "notes": "Purpose-scoped access and reviewed disclosure projections." }, { "dimension": "interoperability", "status": "gap", "notes": "RDAP, origin evidence and flow-export concepts are alignments only." }, { "dimension": "properties", "status": "covered", "notes": "Nonphysical service class, coverage, connectivity and objective properties; physical dimensions belong to infrastructure." }, { "dimension": "recognition", "status": "covered", "notes": "Master reference and scoped evidence identify the service; traffic alone is insufficient." }, { "dimension": "capabilities", "status": "covered", "notes": "Delivery capability, observations and proposed local operations are distinct." }, { "dimension": "source verification", "status": "gap", "notes": "Browser-selected evidence only; coordinator direct HTTP checks pending." } ], "known_omissions": [ "Independent external provider review is absent; local no-tools self-audit is not independent review.", "Direct HTTP status, content hashes, current versions and RFC update/errata chains remain unverified.", "Full E.164 (02/2026), Radio Regulations text and national authority records were not reviewed.", "Nested instance schemas, protocol bindings and executable fixtures are not implemented.", "Technology-specific mobile, satellite, optical, broadcast, emergency-access and accessibility profiles require additional research.", "Commercial settlement, billing, subscriber identity, message contents and network control are outside this root." ], "conflicts": [], "regional_assumptions": [ "International technical references do not establish local legal applicability.", "Numbering, spectrum, privacy, emergency access and retention require an adopting jurisdiction and competent review." ], "adversarial_checks": [ "A phone number can be reassigned without changing or proving service identity.", "Missing observations do not imply zero traffic, success or an outage.", "Registration, route origin validation and actual reachability must not be conflated.", "Aggregation alone does not establish anonymity or release permission.", "An expired grant does not automatically return spectrum or terminate a service." ] }, "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 operator-scoped service provision whose identity survives supported record revisions. Registry standalone-mm describes the record plane, not the subject kind. Resource registries, infrastructure, offerings, parties, commitments and sessions retain separate masters." }, "decisions": [ { "concept": "Service root", "disposition": "accepted", "rationale": "Stable service identity and continuity rules distinguish the entity from a catalogue offering, subscriber number, session or physical cable. Multiple references do not create a multi-master aggregate." }, { "concept": "Legacy F9 domain containment", "disposition": "rejected", "rationale": "The legacy spectrum, addressing, interconnection and traffic concepts are retained as service assertions or external dependencies. Legacy wildcard imports and conformance labels supply no assurance for this draft." }, { "concept": "Spectrum authority", "disposition": "qualified", "rationale": "Only catalogue-level international evidence is available. The result asks for competent authority and profile evidence, allows non-radio services and rejects automatic reversion or permission to transmit." }, { "concept": "Number identity and portability", "disposition": "qualified", "rationale": "The E.164 catalogue edition does not prove a number assignment or portability rule. The result treats these as dated external evidence and does not identify a subscriber or service by number alone." }, { "concept": "Registration, routing and reachability", "disposition": "separated", "rationale": "Registration handles, observed announcements and cache-scoped origin results remain distinct. No origin result is treated as path attestation, reachability or authority to change routes." }, { "concept": "Connectivity and interconnection", "disposition": "accepted with profile qualification", "rationale": "Service-facing demarcation and directed connectivity can reference underlay and interconnection masters without claiming the slice example is a universal telecom schema or exposing internal topology." }, { "concept": "Operational evidence and service requirements", "disposition": "separated", "rationale": "The research entity includes operational evidence alongside references to service requirements. It does not claim that this broader evidence model conforms directly to the customer service model in RFC 8309." }, { "concept": "Coverage, quality and traffic", "disposition": "accepted with evidence limits", "rationale": "Predictions, targets, observed performance and order eligibility remain separate. Measurement scope, units, method and limitations are recorded; absent data is neither zero traffic nor a successful commitment." }, { "concept": "Privacy, retention and integrity", "disposition": "accepted as proposed local policy", "rationale": "Aggregation alone grants no release permission. Scoped access, lawful retention and copy-specific disposal qualify record continuity, while digests and provenance do not certify truth or authenticity." }, { "concept": "Proposed functions", "disposition": "accepted as unimplemented local operations", "rationale": "All six functions require authority, current revision and an applicable profile. Their effects remain local record changes or previews, with explicit refusal outcomes and no network provisioning, collection, route change or resource release." }, { "concept": "Candidate composition", "disposition": "deferred binding", "rationale": "The frozen relationship table contains no model edges. New neighbor links are optional candidates; exact version pins and executable mappings must be reviewed before adoption. No required runtime dependency is silently asserted." }, { "concept": "Source scope and conformance", "disposition": "held", "rationale": "Catalogue and selected-section readings support bounded concepts only. Optional object fields do not form executable instance schemas. Current updates, legal applicability and technology profiles remain explicitly unresolved." }, { "concept": "Independent review", "disposition": "waived and held", "rationale": "Claude and Grok were skipped with zero attempts under the owner override. This separate local Codex self-audit adds no facts and cannot be represented as an independent second-provider review." } ], "publicationHolds": [ "Independent external review is absent. Claude and Grok were skipped with zero attempts under the owner-authorized single-provider waiver; the separate local Codex no-tools self-audit is not independent review.", "Live source and version verification remains incomplete. Direct HTTP was not attempted under the owner-reported sandbox restriction; no HTTP response status or body hash was measured. Selected browser evidence is documented in source-review.md. E.164 and Radio Regulations were read at catalogue level only; RFC updates and errata and current profile applicability remain unverified. The coordinator must run check_sources.py outside the sandbox.", "Adopting jurisdiction and specialist profiles must resolve spectrum, numbering, privacy, retention, emergency access, accessibility and lawful-access obligations. Technology-specific and commercial completeness is not claimed.", "Nested instance schemas, pinned neighbor versions, executable RDAP and telemetry mappings, origin-validation profiles and adversarial fixtures remain incomplete. The local operations are proposals, not runtime capabilities or conformance certification.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Restore independent external review before canonical or publishable-draft promotion.", "Verify current source editions, errata, licensing, full normative texts and applicable national authority records.", "Develop executable profiles and fixtures for number reuse, non-radio service, disputed authority, stale routing evidence, partial outage, missing telemetry, overlapping traffic counters and privacy-preserving disposal." ] }, "statistics": { "sources": 10, "bundles": 6, "layers": 12, "findings": 12, "questions": 36, "artifacts": 12, "functions": 6 } }