Content for AI

Manages

Typed engineering records, ownership, configured lifecycle states and explicit relationships across programme domains.

Produces

A navigable system of record with current context, relationship views and configuration-aware programme outputs.

Boundary

Record types, fields and lifecycle states are configured for the customer’s engineering process.

Reviewed 4 September 2026

Manages

Links between stakeholder needs, system and subsystem requirements, interfaces, architecture, verification records and evidence.

Produces

Trace views, coverage and gap views, impact paths and exportable traceability information for review.

Boundary

Trace quality depends on the programme relationships and applicability rules maintained by the engineering team.

Reviewed 4 September 2026

Manages

Branches, change proposals, diffs, contextual discussion, reviewers, decisions, merges and programme baselines.

Produces

A connected change history showing what changed, why it changed, who reviewed it and which baseline received it.

Boundary

Approval routes and baseline rules follow the customer’s configured authority model.

Reviewed 4 September 2026

Manages

Review scope, named reviewers, due dates, contextual comments, dispositions, approval decisions and completion state.

Produces

An authenticated record of identity, decision, timestamp, reviewed context and subsequent change history.

Boundary

Arc does not present this capability as a regulated electronic-signature certification; contract-specific validation remains a customer decision.

Reviewed 4 September 2026

Manages

Verification methods, test plans, cases, procedures, configurations, executions, results, evidence, status and coverage.

Produces

Coverage views, execution status, requirement-to-evidence chains and review-ready verification records.

Boundary

Acceptance criteria, test authority and evidence sufficiency remain governed by the customer’s programme.

Reviewed 4 September 2026

Manages

Risks, causes, effects, mitigations, failure analysis, defects, anomalies, owners, dispositions and linked corrective work.

Produces

Risk and issue registers, relationship views, accountable dispositions and evidence showing whether affected verification must reopen.

Boundary

Schemas, scoring methods and safety or compliance decisions are tailored to and owned by the customer.

Reviewed 4 September 2026

Manages

Variant definitions, applicability rules, configuration context, shared records, configuration-specific records and baselines.

Produces

Configuration-filtered views, baseline contents and verification coverage for the selected product or mission variant.

Boundary

The customer defines its product-line structure, effectivity rules and configuration authority.

Reviewed 4 September 2026

Manages

Connection scope, authorised fields, identifiers, synchronisation direction, mapping rules and import or export status.

Produces

Synced records, integration events, import reports and controlled round-trip export packages.

Boundary

Arc supports import from CSV, Word, Jira, Git and Confluence. Ongoing synchronisation, connection permissions and interchange behaviour follow the selected deployment and integration scope.

Reviewed 4 September 2026

Manages

Source inventories, field and relationship mappings, identifiers, ownership, import validation, exceptions and reconciliation.

Produces

Connected engineering records, source context, architecture and traceability for the team to inspect before establishing the working baseline.

Boundary

Getting started does not require a six-month migration project. Engineers inspect the imported programme slice and agree the working baseline before expanding adoption.

Reviewed 4 September 2026

Manages

Agent scope, allowed actions, review gates, provider and model choice, organisation-specific retrieval context and self-hosted inference options.

Produces

Immediate findings on unverified changes, missing links, broken traces, requirement conflicts and downstream risks, alongside reviewable proposals and attributable AI-action history.

Boundary

Arc and enabled providers never use customer content to train models; transient inference, retention and provider access follow the selected deployment policy.

Reviewed 4 September 2026

Confirmed by Arc’s founder; reviewed 7 September 2026

Confirmed by Arc’s founder; reviewed 7 September 2026

Confirmed by Arc’s founder; reviewed 7 September 2026

Manages

Customer-scoped access, granular roles, tenant isolation, data residency, model routing and deployment-specific administrative boundaries.

Produces

Exportable audit logs for access, changes, approvals and AI actions, with AES-256 encryption at rest and TLS 1.2 or later in transit.

Boundary

BYODB is a data-ownership option, not a fourth hosting model. Air-gapped environments require no external calls, keep inference local and receive updates through an offline process.

Reviewed 4 September 2026

Manages

Authenticated access to requirements, systems, interfaces, risks, changes, tests and evidence using the caller’s Arc permissions.

Produces

Search results, traceability context, change-impact findings and reviewable record proposals inside the programme workflow.

Boundary

AI tools do not bypass Arc permissions or programme controls. Proposed baseline changes remain subject to the configured human review and merge process.

Updated 15 September 2026