FAQ

Questions about ArchtSoft, answered directly

Straight answers about what ArchtSoft is, how it governs AI coding agents, how it differs from enterprise architecture tools and coding assistants, and what stage the product is actually at.

ArchtSoft is an architecture-driven AI engineering platform built by GRIPACS. ArchtSoft holds one structured, versioned, approved architecture model at the centre of the software engineering lifecycle, and requires AI agents to read from that model before they build anything. The result is that implementation derives from the approved architecture rather than interpreting a document, and every artifact remains traceable back to the requirement that produced it.

Definitions

The terms used on this site

Architecture governance has a vocabulary that is used loosely elsewhere. These are the definitions ArchtSoft works to.

Architecture governance

Architecture governance is the practice of ensuring that the system an organisation runs matches the architecture it approved. Governance becomes enforcement rather than paperwork when the approved design is versioned and implementation is derived from it.

Architecture as a control plane

Treating architecture as a control plane means the architecture model actively directs and constrains what gets built, rather than describing it after the fact. The model becomes a runtime input to the engineering process instead of a document.

Architecture drift

Architecture drift is the widening gap between an approved design and a running system. Drift accumulates with every change implemented without updating the model, and is typically discovered only when remediation has become expensive.

Traceability chain

A traceability chain links each deployed artifact back through integration results, test evidence, code, development tasks, architecture components and decisions, to the business requirement that caused it. An unbroken chain turns an audit into a query.

Architecture simulation

Architecture simulation evaluates how a proposed design will behave — latency, throughput, failure modes, scaling and cost — before implementation begins, so that weaknesses surface while the design is still inexpensive to change.

Security and compliance detail

Question not answered here?

Send it over. You will get a reply from someone who builds the product, not from a sales development queue.