ACS Integration

◉Canonical

Purpose

Business is expected to be one of the largest ACS consumers. ACS supports request analysis, classification, risk detection, missing information extraction, scoping, governance routing, implementation handoff, change request review, and accountability drafting.

ACS does not replace the Business owner. Business consumes ACS capabilities as operational support. It does not provision ACS authority, and ACS support remains review-bound until validated through the correct Business, governance, security, treasury, or domain path.

Scope

This page defines how Business may use ACS outputs and where human, governance, security, treasury, or domain review remains required.

Support Areas

ACS may support:

• request analysis;
• domain and risk classification;
• scoping and acceptance criteria drafts;
• governance route suggestions;
• risk review and claim checks;
• delivery handoffs and Coder task generation;
• change request analysis;
• delivery reporting and accountability notes.

Business Flow

1. Business receives raw request.
2. ACS generates structured summary.
3. ACS extracts required fields and missing information.
4. ACS classifies domain, risk, responsible nucleus, and governance touchpoints.
5. ACS drafts scope questions, governance briefs, or handoff material.
6. Business owner reviews and corrects ACS output.
7. Validated output moves to scope, governance, security review, delivery, or archive.
8. ACS assists change requests and reporting.
9. Validated learning may update knowledge packs.

Output Types

Business ACS outputs may include intake summaries, risk classifications, scope drafts, governance briefs, Coder handoffs, change request analyses, delivery reports, and accountability notes.

Agent Roles

• Morpheus supports strategic fit, governance alignment, narrative clarity, and public-language review.
• Trinity supports operational risk, metrics, monitoring, financial context, and trading or P&L-related analysis where relevant. Trinity remains an analytical support surface consumed by Business, not an institutional decision-maker or direct authority replacement.
• Agent Smith supports adversarial review, scope creep detection, abuse detection, unsafe-claim review, and permission-risk challenge.

Review Requirements

Low-risk requests may require Business owner review. Medium-risk requests should include domain owner review. High-risk requests may require Business, domain, adversarial, governance, or security review. Critical requests require mandatory human review and the appropriate governance, security, treasury, or authority layer.

Boundaries

ACS can summarize, classify, draft, flag, recommend, compare, and generate tasks. ACS cannot commit to client terms, approve budgets, approve governance-sensitive changes, guarantee delivery timeline, promise token or trading outcomes, execute sensitive actions without review, or replace the Business owner.

ACS output is not a client commitment until reviewed and approved through the correct Business or governance path.

Risk Flags

Business should watch for ACS misclassification, client commitment risk, overcompressed summaries, missed governance triggers, unverified claims, and stale memory.

Related Pages

• ACS Overview
• ACS Runtime
• ACS Security and Risk
• Business Runtime

Canonical Traceability

• Integration: INTG-EP8-0008
• Canonical counterpart: ACS Business Integration
• Interfaces: INT-EP7-006, INT-EP7-007
• Authorities: AUTH-EP8-0002, AUTH-EP8-0012
• Evidence: EVID-EP7-0006, EVID-EP7-0008
• Status: prototype/model; ACS remains advisory and Business owns disposition.