CAIRNS trial, demonstration build
Self-guided, ten minutes

Walk the demonstration build.

This is Cairns running on a fully synthetic estate at the scale of a Commonwealth regulator: 300 applications, 4,000 configuration items, 1,000 controls, and a 43-document corpus of design documents, board minutes and decision records. Every person, application, document and decision in it is generated. Nothing here is anyone's data.

What is real and what is not. The software is real: the ingestion, provenance pins, reconciliation, change detection, answers and refusals all work. The estate is synthetic and labelled as such throughout. The natural-language answers in this build run on deterministic demonstration intents; in production the same intents run with a screened model in front of the same repository.

The walk, nine stops

  1. The estate, honestly imperfect.app/#/
    Dashboard. 384 configuration items already past end of support, 726 with no lifecycle date at source. The missing dates route to an enrichment queue; nothing is guessed.
  2. Ask a question, get a cited answer.app/#/ask-eol
    Which applications run technology due within 18 months? The answer is computed from pinned records and carries its sources. Figures are computed, never written by a model.
  3. Ask a question it cannot answer.app/#/ask-refuse
    The platform refuses and logs the refusal. An architecture tool a regulator can defend does not invent.
  4. Watch the corpus change.app/#/changes
    A waiver revoked in board minutes; a design decision superseded. Diffs with before-and-after hashes, both versions retained, affected records queued. Below: three shadow applications found in documents but absent from the CMDB.
  5. One application, end to end.app/#/app/APP-0223
    Custodians, capabilities, technology positions, the documents that mention it with their sha256 pins, controls, decisions. This is the application whose design document changed at stop four.
  6. Put a draft against the model.app/#/submit-sample
    Allocate a draft design and run impact analysis: what it touches, the exposure it inherits, the waiver that changed state this week, the uncatalogued technology it proposes, and where it must route. Co-design, not late-stage review.
  7. Draw on the record.app/#/canvas/...
    The design canvas: elements from the register, solid links from the record, and a proposed link drawn on the canvas (dashed) that writes the model when approved. A diagram that cannot drift from the record.
  8. Analytics, reports and the gap register.app/#/analytics · app/#/reports · app/#/gaps
    Charts computed from the record with their basis stated. A report builder that composes sections and exports. And the gap register: enterprise-level gaps with severities and suggested treatments, each linked to the workflow that closes it.
  9. Throw the master switch.app/#/ai
    The AI disclosure register: every feature, its model, its data, its retention, its switch. Turn the master switch off, then open Ask Cairns: the platform continues, the AI does not. Your switch state persists only in your own browser.

Notes

QuestionAnswer
Why synthetic?A demonstration on a real agency's estate would be a disclosure. The synthetic estate is built to the buyer's stated scale and deliberately carries the same failure modes: missing owners, stale lifecycle data, documents that conflict with the register, applications that were never registered.
What happens to my inputs?Nothing leaves your browser. The build is static files; switch states sit in local storage on your machine.
Can we get a walkthrough?Yes: contact@bluebirdadvisory.com.au. We also run demonstrations against your own scenarios.