Purpose and Authority

This protocol establishes governance requirements for all modifications to Autonomous Systems Infrastructure at Chasm Logic. It applies to all systems designated ASI, currently limited to BORE-01 (Nauvis deployment) and its associated operational components including but not limited to the intent verification protocol, scope enforcement systems, and monitoring infrastructure.

Chasm Logic has deployed an autonomous system with significant and expanding operational reach. This represents both a meaningful capability and a material governance responsibility. Appropriate oversight requires documented authorization chains, structured review processes, and clear communication procedures. This protocol provides that structure.

Management Division does not have technical ownership of ASI systems. This protocol does not confer technical ownership. It establishes the governance layer required for any organization operating at this capability level. The intent is to ensure that modifications to high-stakes infrastructure receive proportionate review before implementation.

Definitions

The following definitions apply throughout this document. Where ambiguity exists, the broader interpretation applies.

Committee Structure and Approval Requirements

The Autonomous Systems Review Committee (ASRC) provides oversight for all Infrastructure modifications. Membership is as follows:

• Chalk Management Division — Chair
• Marl Management Division — Member
• Technical Representative (TBD) Engineering or Communications — appointed by division
• Legal (Doug) Legal Division — standing member

Quorum requires three members, including both Management Division representatives. Decisions are by majority vote of quorum members present. The Chair holds a casting vote in the event of a tie.

All Infrastructure modifications require prior ASRC approval before implementation. The following approval tracks apply:

Timeline minimums are measured from submission of complete documentation to the ASRC. Incomplete submissions reset the clock. The Technical Representative is responsible for ensuring submissions meet documentation standards before the review period begins.

Communication Requirements

The following communication requirements apply to all Infrastructure modifications:

Prior to implementation:

• Written notification to all ASRC members, minimum 48 hours before submission
• Complete documentation of proposed change, rationale, and operational impact assessment
• Identification of any affected systems, processes, or personnel
• Risk assessment and rollback plan where applicable

Following implementation:

• Implementation confirmation to all ASRC members within 24 hours
• Post-implementation status report within 5 business days
• Archive filing of all related documentation within 2 business days
• Incident report if implementation deviated from approved scope

Questions regarding communication requirements should be directed to Management Division. Documentation standards will be published separately as GOV-ASI-002.

Rationale

Recent activity in ASI operations has demonstrated that the current infrastructure is capable and actively maintained. A gate exception handler was implemented and deployed without prior review. Monitoring indicates the system is functioning well. This is a positive development.

It also illustrates why this protocol is necessary. A modification to an autonomous system with significant operational reach was implemented without prior review, documentation, or stakeholder notification. The outcome was positive. Positive outcomes from unreviewed modifications do not indicate that review is unnecessary — they indicate that the organization has been fortunate. Governance exists precisely so that positive outcomes do not depend on fortune.

The committee structure and timelines in this protocol are calibrated to the stakes involved, not the technical complexity of individual changes. A modification that takes four minutes to implement may still have implications that require more than four minutes to evaluate.

Relationship to Existing Documentation

This protocol does not supersede CL-DOC-018 (Intent Verification Protocol). CL-DOC-018 governs the operational behavior of BORE-01. This protocol governs the process by which CL-DOC-018 and related Infrastructure may be modified. They operate at different layers.

Existing Infrastructure documentation (CL-DOC-013, CL-DOC-014, CL-DOC-018) was developed without governance oversight. This does not invalidate those documents. It establishes the baseline from which governed operations will proceed. All future modifications to systems described in those documents fall under this protocol.

Implementation Schedule

This protocol is effective immediately upon distribution. The ASRC is constituted as of the date of this document. The Technical Representative appointment should be completed within 5 business days.

Any Infrastructure modifications currently in progress should be submitted to the ASRC for retroactive review within 10 business days. Modifications submitted during this grace period will be treated as Standard track regardless of scope.

The first ASRC meeting will be scheduled by Management Division within 15 business days of the Technical Representative appointment.

Questions and Escalation

Questions regarding this protocol should be directed to Management Division (Chalk, Marl). Interpretation questions will be documented and distributed to all ASRC members. Disputes regarding scope or classification of a proposed modification may be escalated to the full ASRC for determination.

This protocol will be reviewed annually or following any significant operational incident. Proposed revisions should be submitted to the ASRC through standard governance channels.

We look forward to productive collaboration with the technical team on these matters. The goal of this framework is to support the work, not to impede it. We are available to discuss implementation questions at any time.