At a glance
| Scope | Current status | Function | Boundary |
|---|---|---|---|
| Terminology governance | Production v6 | Create, review, approve, deprecate, and version terms | The last content editor cannot approve that content. |
| Confluence usage | Production v6 | Scan pages, record findings, publish approved terms, and export audit records | Results depend on accessible pages and completed scans. |
| Readiness mapping | Production v6 | Compare required-term catalogs with governed terms | A readiness score reflects terminology coverage. It is not a compliance determination. |
| Cross-space terminology | Production v6 | Use approved terms from subscribed source spaces | Personal spaces are excluded from subscription controls. |
| Legacy terminology baseline | Production v6 compatibility path | Freeze term states and scanned-page references, then report changes, usage, and coverage | The path is bounded and shows truncation or unsupported coverage states. |
| Enterprise evidence workspace | Production v6 | Queue evidence freezes, inspect exact revisions, traverse traces, verify evidence, and process archives | Deployment is confirmed. Forge staging qualification and measured capacity remain unrecorded. |
| External handoff | Production v6 | Download a glossary slice or reissue-handoff JSON file | The file requests an external action. The app does not perform or approve that action. |
Production terminology workflow
- A term manager creates a definition in Terms.
- One person edits and submits it for review.
- A different eligible person selects Approve.
- Compliance Scanner checks accessible pages for governed terminology issues.
- Page owners resolve findings with recorded evidence.
- Compliance Glossary and Glossary term macros publish approved definitions.
- Audit Evidence Export produces the supported audit record set.
Legacy baseline path
Production v6 keeps Create baseline available. It records bounded term states and scanned-page references for selected spaces.
The view reports changed terms, changed pages, usage, impact, and coverage warnings. This path remains separate from the enterprise storage model.
Enterprise workspace status
Production v6 mounts Enterprise evidence workspace under Terminology Baseline. Its resolvers, queues, SQL storage, Object Store, and visible controls are deployed.
The workspace includes Prepare and queue freeze, Run verification, Forward impact, Reverse provenance, archive operations, slices, handoffs, and file evidence.
Forge CLI records production version 6 as deployed on 2026-09-26 at 13:58:58.031 UTC.
The deployed definition includes SQL, Object Store, LLM, 12 functions, four consumers, and one backend egress entry.
Deployment confirms availability. It does not establish Forge staging qualification, measured performance, consumption, cost, production capacity, or physical residency.
Example
A policy team governs “material incident.” A separate person approves its definition. The scanner finds an older synonym and records the affected pages.
Production v6 supports finding review, macros, audit export, and enterprise tracing from implementation to a retained business or regulatory basis.
External approval boundary
Compliance Glossary governs terminology and records related evidence. It does not certify an organization, approve a Confluence page, or approve a software release.
It does not execute signatures or replace a QMS. The handoff contains instructions and evidence references for an external downstream action.
A person or connected external system must complete and approve that action.
Related questions
Next step
Use production v6 for governed terminology and connected evidence. Keep deployment evidence separate from qualification, capacity, residency, and external approval claims.
View on Atlassian Marketplace