{ "vercy": "1.0-draft", "publication": { "status": "research-draft", "adjudicationStatus": "unreviewed", "publishableCanonical": false, "generatedAt": "2026-09-12T09:10:27Z", "providers": [ "Codex" ], "breadth": "recalled by Codex without web access - no source was read", "missingProviders": [], "pass": 2, "cost": { "grok": { "seconds": 28.0, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a094e0-ba29-7d42-a292-08caf548ecc5\n--------\nuser\nDescribe what is already known about one registered thing. Answer as JSON only, no prose around it.\n\nThing: Digital Signal 1\nSense to describe: (none recorded)\nDomain code: ACT.ACT\nAlso known as: (none)\n\n\nContext for this batch of 1001 things:\n# Batch 043: 100", "usd": 0.0, "recall": true }, "codex": { "seconds": 77.4, "error": "Reading additional input from stdin...\nOpenAI Codex v0.153.4\n--------\nworkdir: R:\\02_PROJECTS\\02_Meta_Models_Platforms\\Ver.cy\\current\\thing-registry-backlog\nmodel: gpt-6-astra\nprovider: openai\napproval: never\nsandbox: read-only\nreasoning effort: none\nreasoning summaries: none\nsession id: 01a094e0-ba1b-77a0-b15c-b3e0c8b33e68\n--------\nuser\nYou are drafting a Vercy meta-model for one registered thing. Answer as JSON only, no prose around it.\n\nThing: Digital Signal 1\nRegistry id: vr.tr.digital-signal-1\nPlane / domain: ACT / ACT.ACT\nRegistry definition: (none recorded)\nNames folded into this entry:" } }, "enrichment": { "pass": 3, "engine": "claude", "producedAt": "2026-10-06T12:00:00Z", "ingestedAt": "2026-10-06T08:45:15+00:00", "fields": [ "agent_conduct", "ethics", "failure_modes_and_hazards", "owners", "standards_and_regulation", "visual_identification" ] }, "gate": { "passed": true, "version": "1.0", "at": "2026-10-07T10:10:28+00:00", "evidence": [ "completeness 1.00", "sense: Wikidata description", "2 live sources", "review by codex: pass" ] } }, "metaModel": { "id": "THING-Q2180989", "registryId": "vr.tr.digital-signal-1", "name": "Digital Signal 1", "version": "0.1.0-research.1", "entryKind": "thing", "family": "Thing Registry", "domain": [ "ACT.ACT" ], "status": "research-draft" }, "canonicalUrl": "https://ver.cy/models/thing/q2180989/", "model": { "registry_id": "vr.tr.digital-signal-1", "name": "Digital Signal 1", "purpose": "Enable an agent to recognise a Digital Signal 1 instance, assess its configuration and transmission state, and determine compatible provisioning or diagnostic actions.", "definition": "Digital Signal 1 (DS1) is a level in the North American digital transmission hierarchy with a nominal bit rate of 1.544 Mbit/s, conventionally structured as 24 channels of 64 kbit/s plus framing overhead.", "scope_statement": "This model owns the DS1 signal format and the evidence needed to evaluate its operational instances under vr.tr.digital-signal-1, including framing, payload allocation, timing, interface compatibility and fault interpretation.", "in_scope": [ "DS1 identity and its relationship to T1 transport and service terminology", "Nominal transmission rate, frame structure and framing variants", "DS0 allocation, aggregate payload use and signalling constraints", "Endpoint line coding and clock compatibility", "Directional alarms, performance evidence and diagnostic actions" ], "out_of_scope": [ "Physical construction and maintenance of T1 cables, repeaters and connectors", "Complete models of DS0, E1, J1, DS3 and other hierarchy members", "Voice codecs, call control and application protocols carried by DS1", "Internal architecture of channel banks, multiplexers and CSU/DSU equipment", "Carrier pricing, service contracts and network-wide routing" ], "distinguishing_features": [ "DS1 has a nominal line rate of 1,544,000 bit/s; E1 has a nominal rate of 2,048,000 bit/s. Rate alone does not distinguish DS1 from J1. [RFC 4805](https://www.rfc-editor.org/rfc/rfc4805.html)", "A conventional framed DS1 repeats 193-bit frames at 8,000 frames/s, with 192 payload bits and one framing bit.", "DS1 denotes the digital signal level; a reference to T1 must be resolved as transport, interface or service usage before treating it as the same modelled instance.", "D4/SF, ESF and unframed configurations must be distinguished; an interface may support several without using them simultaneously. [Cisco DS1 interface specifications](https://www.cisco.com/c/en/us/products/collateral/interfaces-modules/ons-15454-sonet-56-port-ds-1-e1-card/product_data_sheet0900aecd8031a1de.html)", "A fractional allocation uses selected capacity within a DS1 bearer; it does not establish a different nominal DS1 line rate." ], "characteristics": [ { "name": "Nominal line rate", "kind": "measurement", "unit_or_values": "1,544,000 bit/s", "why_it_matters": "Identifies the signal rate without equating it to application throughput." }, { "name": "Framing mode", "kind": "category", "unit_or_values": "D4/SF; ESF; unframed; other documented profile; unknown", "why_it_matters": "Determines receiver alignment requirements and available monitoring mechanisms." }, { "name": "Electrical line coding", "kind": "category", "unit_or_values": "AMI; B8ZS; other documented profile; not applicable at this observation point; unknown", "why_it_matters": "Controls compatibility and interpretation of pulse patterns at an electrical termination." }, { "name": "Payload allocation", "kind": "relation", "unit_or_values": "Association of DS0 positions 1-24 or aggregate payload with services", "why_it_matters": "Makes partial provisioning, cross-connect errors and affected services identifiable." }, { "name": "Signalling arrangement", "kind": "category", "unit_or_values": "Robbed-bit channel-associated signalling; common-channel signalling; no in-band signalling; other; unknown", "why_it_matters": "Determines whether payload bits or channels are reserved for signalling." }, { "name": "Transmit clock source", "kind": "relation", "unit_or_values": "Internal oscillator; recovered receive clock; external reference; equipment-specific source", "why_it_matters": "Supports detection of incompatible timing plans and timing loops." }, { "name": "Receive condition", "kind": "state", "unit_or_values": "Observed combinations of signal present, frame aligned, LOS, LOF, AIS and remote alarm, with timestamp and direction", "why_it_matters": "Separates local reception failures from indications reported by a remote endpoint." }, { "name": "Transmission performance", "kind": "measurement", "unit_or_values": "Applicable error counts, errored seconds, severely errored seconds, unavailable seconds and slips per stated observation interval", "why_it_matters": "Supports assessment of intermittent impairment while preserving counter definitions and interval validity." } ], "affordances": [ "Classify a documented or measured signal as DS1 and identify unresolved profile details.", "Compare endpoint framing, line coding, clocking and payload assignments before provisioning.", "Trace a DS0 or aggregate service to the DS1 capacity it occupies.", "Interpret alarms and performance counters to select the next diagnostic observation.", "Plan an authorised loopback or bit-error test with explicit traffic impact and restoration checks.", "Evaluate whether a replacement bearer preserves required payload and timing behaviour." ], "agent_conduct": { "may": [ "Explain the DS1 signal structure and its relation to T1 lines.", "Monitor DS1 links on networks the agent is authorized to manage." ], "must_not": [ "Intercept or tap DS1 traffic on lines the agent does not operate.", "Disrupt circuits that carry emergency or critical services.", "Reconfigure carrier equipment without authorization." ], "requires_human": [ "Decommissioning legacy circuits that critical services may depend on." ] }, "ethics": { "considerations": [ "Legacy telephone circuits still carry critical communications.", "Communications privacy is protected by law." ], "affected_parties": [ "Network users", "Emergency services", "Network operators" ] }, "owners": { "steward": "Nobody owns the standard; the carrier or operator answers for each circuit.", "master_systems": [] }, "visual_identification": [ "Not visible; carried on copper pairs or fibre and terminated on network equipment with T1 ports." ], "failure_modes_and_hazards": [ "Framing or timing errors cause call and data loss.", "Unplanned decommissioning can cut off dependent services." ], "standards_and_regulation": [ "ITU-T Recommendation G.704, Synchronous frame structures used at 1544, 6312, 2048, 8448 and 44 736 kbit/s hierarchical levels, International Telecommunication Union.", "ANSI T1.403 Network and Customer Installation Interfaces, DS1 Electrical Interface, American National Standards Institute." ], "what_it_is_for": [ "Digital Signal 1 is encountered in North American telecommunications infrastructure carrying aggregated voice channels or digital data.", "It is used at interfaces between carrier equipment, customer premises equipment and transmission systems, particularly in legacy installations.", "Its framing and channel structure matter when provisioning circuits, checking compatibility and interpreting transmission faults." ] }, "sources": [ { "id": "wikidata", "title": "Wikidata item Q2180989: Digital Signal 1", "url": "https://www.wikidata.org/wiki/Q2180989", "url_status": "live", "what_it_supports": "identity and sense of the item", "checked_by": "wikidata-api" }, { "id": "wikipedia-en", "title": "Wikipedia: Digital Signal 1", "url": "https://en.wikipedia.org/wiki/Digital_Signal_1", "url_status": "live", "what_it_supports": "general description of the item", "checked_by": "wikidata-api sitelink" } ], "structure": { "bundles": [ { "id": "ds1-identity-and-profile", "name": "DS1 identity and profile", "description": "Establish what a DS1 label denotes and which technical profile governs the instance.", "rationale": "A service label or shared interface type is insufficient to establish signal compatibility.", "layers": [ { "id": "signal-and-bearer-boundary", "name": "Signal and bearer boundary", "description": "Separate the DS1 signal from equipment, physical transport and commercial service.", "findings": [ { "id": "ds1-instance-evidence", "name": "DS1 instance evidence", "description": "Record whether identification rests on configuration, a service record or an observed signal.", "questions": [ { "text": "What evidence identifies this instance as a DS1 signal rather than merely a service sold as T1?", "kind": "definition", "id": "ds1-instance-evidence-q01" }, { "text": "Which port, transport path and service records refer to this same signal instance?", "kind": "boundary", "id": "ds1-instance-evidence-q02" } ] } ] }, { "id": "applicable-ds1-profile", "name": "Applicable DS1 profile", "description": "Identify the specification and implementation conventions used by each termination.", "findings": [ { "id": "profile-agreement", "name": "Profile agreement", "description": "Record the applicable profile explicitly, including regional distinctions; DS1 and J1 share a nominal rate but have differences in alarm behaviour. [RFC 4805](https://www.rfc-editor.org/rfc/rfc4805.html)", "questions": [ { "text": "Which specification revision and equipment documentation define the endpoint profile?", "kind": "provenance", "id": "profile-agreement-q01" }, { "text": "What evidence distinguishes this profile from J1 or an E1 interface represented by the same management interface type?", "kind": "boundary", "id": "profile-agreement-q02" } ] } ] } ] }, { "id": "frame-and-payload-organisation", "name": "Frame and payload organisation", "description": "Describe how the DS1 bitstream is aligned and assigned to useful traffic.", "rationale": "Matching line rates does not guarantee matching framing or delivery to the correct channel.", "layers": [ { "id": "frame-alignment", "name": "Frame alignment", "description": "Capture configured and detected framing at each endpoint.", "findings": [ { "id": "framing-mode-agreement", "name": "Framing mode agreement", "description": "Distinguish D4/SF, ESF and intentionally unframed operation, recording receiver alignment separately from configuration.", "questions": [ { "text": "What framing mode is configured and what mode is actually detected in each direction?", "kind": "measurement", "id": "framing-mode-agreement-q01" }, { "text": "Does absent frame alignment indicate a fault or intentional unframed operation?", "kind": "boundary", "id": "framing-mode-agreement-q02" } ] } ] }, { "id": "payload-capacity-and-assignment", "name": "Payload capacity and assignment", "description": "Relate framed payload capacity to channel allocation and service use.", "findings": [ { "id": "channel-allocation-consistency", "name": "Channel allocation consistency", "description": "Record assignment of the 24 eight-bit payload positions or their aggregate use; conventional framing provides 1,536,000 payload bit/s before service-specific deductions.", "questions": [ { "text": "Which positions carry each service, and which are idle, reserved or unavailable?", "kind": "measurement", "id": "channel-allocation-consistency-q01" }, { "text": "Do channel numbering and grouping agree at both terminations and intermediate cross-connects?", "kind": "boundary", "id": "channel-allocation-consistency-q02" }, { "text": "What usable service rate remains after signalling reservations and protocol overhead?", "kind": "measurement", "id": "channel-allocation-consistency-q03" } ] } ] } ] }, { "id": "signalling-and-bit-transparency", "name": "Signalling and bit transparency", "description": "Identify how signalling and line coding affect preservation of payload bits.", "rationale": "A DS1 can carry traffic successfully while still failing a service's requirement for transparent data transport.", "layers": [ { "id": "payload-signalling-use", "name": "Payload signalling use", "description": "Identify signalling carried within channel bits or reserved channels.", "findings": [ { "id": "signalling-reservations", "name": "Signalling reservations", "description": "Record robbed-bit use and any dedicated signalling channel without assuming that every DS1 carries telephone calls.", "questions": [ { "text": "Which channels, if any, use robbed-bit signalling, and under which framing arrangement?", "kind": "definition", "id": "signalling-reservations-q01" }, { "text": "Does the intended service require every payload bit to be preserved?", "kind": "boundary", "id": "signalling-reservations-q02" } ] } ] }, { "id": "electrical-bit-encoding", "name": "Electrical bit encoding", "description": "Relate electrical encoding to endpoint compatibility and payload requirements.", "findings": [ { "id": "line-code-compatibility", "name": "Line-code compatibility", "description": "DS1 electrical interfaces commonly offer AMI and B8ZS; record the selected mode at each applicable termination. [Cisco DS1 interface specifications](https://www.cisco.com/c/en/us/products/collateral/interfaces-modules/ons-15454-sonet-56-port-ds-1-e1-card/product_data_sheet0900aecd8031a1de.html)", "questions": [ { "text": "Which line code is configured and detected at each electrical termination?", "kind": "measurement", "id": "line-code-compatibility-q01" }, { "text": "What documented pulse-density or zero-suppression restrictions constrain this payload?", "kind": "boundary", "id": "line-code-compatibility-q02" }, { "text": "What coordinated configuration changes are needed to satisfy the service's bit-transparency requirement?", "kind": "action", "id": "line-code-compatibility-q03" } ] } ] } ] }, { "id": "clocking-and-transport-continuity", "name": "Clocking and transport continuity", "description": "Track timing dependencies and preservation of DS1 through its bearer path.", "rationale": "Correct framing and channel assignments cannot compensate for unstable timing or an incompatible adaptation.", "layers": [ { "id": "clock-source-chain", "name": "Clock source chain", "description": "Record where each transmitter obtains timing and how dependencies connect.", "findings": [ { "id": "timing-plan-consistency", "name": "Timing plan consistency", "description": "Require an explicit clock-source chain and evidence of timing stability.", "questions": [ { "text": "What clock drives each transmit direction, and which upstream reference ultimately supplies it?", "kind": "provenance", "id": "timing-plan-consistency-q01" }, { "text": "What measured slips or clock-source changes suggest a timing loop or reference mismatch?", "kind": "measurement", "id": "timing-plan-consistency-q02" } ] } ] }, { "id": "bearer-adaptation", "name": "Bearer adaptation", "description": "Identify boundaries where DS1 is carried through another transport technology.", "findings": [ { "id": "adaptation-preservation", "name": "Adaptation preservation", "description": "Record what each adaptation preserves, regenerates or terminates, including framing, timing and alarm information.", "questions": [ { "text": "Where is this DS1 multiplexed, encapsulated or regenerated along its path?", "kind": "boundary", "id": "adaptation-preservation-q01" }, { "text": "Which payload, timing and alarm behaviours does each adaptation promise to preserve?", "kind": "provenance", "id": "adaptation-preservation-q02" }, { "text": "What evidence is required before substituting a different bearer?", "kind": "action", "id": "adaptation-preservation-q03" } ] } ] } ] }, { "id": "fault-evidence-and-testing", "name": "Fault evidence and testing", "description": "Convert DS1 observations into bounded diagnostic and restoration decisions.", "rationale": "Alarm direction, counter validity and loopback location determine what a test can establish.", "layers": [ { "id": "directional-health-evidence", "name": "Directional health evidence", "description": "Interpret defects and accumulated impairment at identified observation points.", "findings": [ { "id": "alarm-and-counter-interpretation", "name": "Alarm and counter interpretation", "description": "Record local and remote indications separately, with applicable counter definitions, interval validity and unavailable-time treatment. [RFC 4805](https://www.rfc-editor.org/rfc/rfc4805.html)", "questions": [ { "text": "Which endpoint and receive direction report LOS, LOF, AIS or remote alarm, and when did each indication begin?", "kind": "measurement", "id": "alarm-and-counter-interpretation-q01" }, { "text": "Which error counters are valid for this framing mode, and over what complete observation interval?", "kind": "measurement", "id": "alarm-and-counter-interpretation-q02" }, { "text": "What additional observation would distinguish framing mismatch, timing impairment and bearer failure?", "kind": "action", "id": "alarm-and-counter-interpretation-q03" } ] } ] }, { "id": "loopback-and-restoration", "name": "Loopback and restoration", "description": "Define the diagnostic reach and operational consequences of intrusive tests.", "findings": [ { "id": "bounded-diagnostic-test", "name": "Bounded diagnostic test", "description": "Record loopback location, test direction, pattern, duration, expected result and restoration evidence.", "questions": [ { "text": "Which DS1 segment will this loopback and test pattern exercise, and which faults remain outside its reach?", "kind": "boundary", "id": "bounded-diagnostic-test-q01" }, { "text": "Which services will the test interrupt, and what authorisation covers that interruption?", "kind": "action", "id": "bounded-diagnostic-test-q02" }, { "text": "What observations will confirm loopback removal, restored configuration and acceptable service performance?", "kind": "action", "id": "bounded-diagnostic-test-q03" } ] } ] } ] }, { "id": "evidence-and-external-alignment", "name": "Evidence and external alignment", "description": "What the world already says about this thing, gathered so the model can be checked against it.", "rationale": "A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.", "layers": [ { "id": "reported-evidence", "name": "Reported evidence", "description": "Findings from the breadth pass, kept separate from the structural claims.", "findings": [ { "id": "evidence-confidence-notes", "name": "Check these first", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "This is recalled technical knowledge; no sources were consulted.", "Check the applicable editions and current designations of ANSI/ATIS standards before using this description for compliance.", "The name strongly indicates the telecommunications sense; the supplied ACT.ACT domain code does not establish a different sense." ], "questions": [ { "id": "evidence-confidence-notes-q01", "text": "Which of these check these first hold for the sense of Digital Signal 1 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-kinds", "name": "Kinds and varieties", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Superframe (SF, also called D4) framing", "Extended Superframe (ESF) framing", "Unframed DS1" ], "questions": [ { "id": "evidence-kinds-q01", "text": "Which of these kinds and varieties hold for the sense of Digital Signal 1 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-identifiers", "name": "Identifiers and schemes", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "scheme": "Digital signal hierarchy designation", "value_or_pattern": "DS1", "note": "Identifies a signal level and format, rather than a particular circuit or physical cable." } ], "questions": [ { "id": "evidence-identifiers-q01", "text": "Which of these identifiers and schemes hold for the sense of Digital Signal 1 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-standards-and-regulation", "name": "Standards and regulation", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "ANSI T1.107, Digital Hierarchy - Formats Specifications, developed through Committee T1/ATIS", "ANSI T1.403, metallic interfaces for DS1 electrical access to telecommunications networks, developed through Committee T1/ATIS", "ITU-T Recommendation G.703, physical and electrical characteristics of hierarchical digital interfaces", "ITU-T Recommendation G.704, synchronous frame structures including the 1544 kbit/s hierarchy level" ], "questions": [ { "id": "evidence-standards-and-regulation-q01", "text": "Which of these standards and regulation hold for the sense of Digital Signal 1 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-real-world-use", "name": "Real-world use", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Multiplexing 24 conventional digital telephone channels", "Providing leased digital connections for enterprise data networks", "Connecting private branch exchanges to telephone networks", "Carrying ISDN Primary Rate Interface service, commonly with 23 bearer channels and one signalling channel", "Serving as a tributary within higher-rate digital transport systems" ], "questions": [ { "id": "evidence-real-world-use-q01", "text": "Which of these real-world use hold for the sense of Digital Signal 1 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-measurements", "name": "Typical measurements", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "quantity": "Nominal aggregate bit rate", "typical_range": "1.544", "unit": "Mbit/s" }, { "quantity": "Conventional framed signal frame length", "typical_range": "193", "unit": "bits" }, { "quantity": "Frame repetition rate", "typical_range": "8000", "unit": "frames/s" }, { "quantity": "Nominal channel bit rate", "typical_range": "64", "unit": "kbit/s" }, { "quantity": "Aggregate channel capacity before service-specific signalling overhead", "typical_range": "1.536", "unit": "Mbit/s" } ], "questions": [ { "id": "evidence-measurements-q01", "text": "Which of these typical measurements hold for the sense of Digital Signal 1 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-failure-modes-and-hazards", "name": "Failure modes and hazards", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "Loss of signal or frame alignment interrupts service.", "Clock mismatch can cause slips and corrupt carried voice or data.", "Excessive jitter or wander can impair reception and synchronisation.", "Mismatched framing or line-code configurations can prevent correct operation.", "Robbed-bit signalling reduces the bits available for transparent user data in affected channels." ], "questions": [ { "id": "evidence-failure-modes-and-hazards-q01", "text": "Which of these failure modes and hazards hold for the sense of Digital Signal 1 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-regional-variation", "name": "Regional variation", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ "DS1/T1 is historically associated especially with North American telecommunications networks.", "Many other regions use E1 at 2.048 Mbit/s, with a different frame structure.", "Japan uses the related J1 system at 1.544 Mbit/s, with interface and operational differences requiring compatibility checks." ], "questions": [ { "id": "evidence-regional-variation-q01", "text": "Which of these regional variation hold for the sense of Digital Signal 1 this model covers, and on what evidence?", "kind": "provenance" } ] }, { "id": "evidence-neighbours", "name": "Neighbouring kinds and how to tell them apart", "description": "Recalled without web access and unsourced; every item is a lead to verify.", "evidence": [ { "name": "T1", "difference": "T1 denotes the carrier transmission system commonly used to convey DS1; DS1 denotes the digital signal and hierarchy level." }, { "name": "DS0", "difference": "DS0 is a 64 kbit/s channel; a conventionally channelised DS1 contains 24 such channels plus framing overhead." }, { "name": "E1", "difference": "E1 operates at 2.048 Mbit/s and conventionally uses 32 time slots, rather than the DS1 rate and frame structure." }, { "name": "Fractional T1", "difference": "Fractional T1 service allocates a subset of the channels carried by a full-rate DS1 connection." }, { "name": "ISDN Primary Rate Interface", "difference": "PRI is a bearer-and-signalling service arrangement that can use DS1 or E1 transport; it is not itself a digital hierarchy level." } ], "questions": [ { "id": "evidence-neighbours-q01", "text": "Which of these neighbouring kinds and how to tell them apart hold for the sense of Digital Signal 1 this model covers, and on what evidence?", "kind": "provenance" } ] } ] } ] } ] }, "openQuestions": [ "Which normative specification revisions should anchor the registry's DS1 definition and its boundary with J1?", "Does an existing Vercy world model already own DS1 or an equivalent concept, requiring this entry to link to it?", "Which unframed and historical DS1 profiles must the model support beyond D4/SF and ESF?", "Which profile-specific thresholds and observation rules should determine degraded, failed and restored states?", "How should the ACT / ACT.ACT placement be reconciled with DS1's identity as a signal format while preserving the registered entry?" ], "statistics": { "bundles": 6, "layers": 11, "findings": 19, "questions": 34 } }