Compliance Glossary for Confluence

Can Compliance Glossary support 200,000 pages?

Not as a verified Forge production claim. Compliance Glossary has no measured result for 200,000 Confluence pages. A local deterministic simulation processed 250,000 mixed artifacts across eight classes. One class represented Confluence documents. It recorded recovery and modeled resource signals. It did not measure Forge latency, consumption, cost, data residency, or tenant throughput. Production capacity remains unqualified.

Last verified against production v6 · 26 September 2026

At a glance

InputActionOutputLimit
Selected Confluence spacesCount persisted terms, pages, usages, and findingsSeven-part demand estimateCounts cover the selected scanned scope only
Freeze estimateCompare demand with policy bounds before writesAccepted or rejected decisionAcceptance is a safety gate, not a benchmark
Page and term evidenceProcess up to 100 source units per worker pageResumable freeze with checkpointsCompletion time still depends on live Forge and tenant data
Local qualification workloadStream 250,000 fixtures across eight artifact classesRecovery records, roots, and modeled metricsNot Forge latency, cost, consumption, residency, or throughput evidence
Confluence-document fixture classGenerate 31,250 of the 250,000 local artifactsDeterministic document-shaped recordsFixtures are not live Confluence pages
200,000-page targetReplay a representative workload in ForgeMeasured pass or documented constraintNo completed Forge qualification result is recorded

How it works

  1. Define the target page count, content size, term density, findings, links, and files.
  2. Record the deployed Forge version, environment, migration, dependencies, and data shape.
  3. Run capacity admission for the selected scope.
  4. Replay a representative workload in an authorized Forge environment.
  5. Measure latency, duration, failures, recovery, events, storage, and cost.
  6. Publish the measured result with its exact conditions and limits.

Example

A team has 200,000 Confluence pages across many spaces. Capacity admission can estimate a selected, scanned baseline and block work above policy bounds. It cannot prove completion time for the full site. The local 250,000-artifact simulation contains 31,250 Confluence-document fixtures, not 250,000 live pages. A representative Forge run remains necessary.

What this does not mean

Bounded processing and admission checks are engineering controls. They are not benchmark results. The harness marks Forge latency and cost evidence as false. Current qualification records contain no completed Forge staging or production measurement. No verified 200,000-page capacity claim should be published.

Related questions

Create Enterprise Baseline ConfluenceBaseline Coverage BlockersCompliance Glossary Limitations

Next step

Evaluate the intended scope before adopting a scale assumption.

View on Atlassian Marketplace
Verification basis: production v6 code, tests, manifest, and operations guidance. Verified 26 September 2026.