What is Balcony?

Balcony is where governance design happens. Rather than treating compliance as a documentation exercise, it treats governance as an engineering problem: one that requires real mechanisms behind every control, not just policies on paper.

The platform is built around a single analytical chain that practitioners work through iteratively:

Artefact → Expectation → Control → Mechanism

Nexus handles the left half of this chain. It maps what external frameworks — regulations, standards, contracts — actually require against a unified control structure. The result is a crosswalk: a live picture of where requirements converge, where they diverge, and where gaps exist.

Mechanic handles the right half. It takes each control from the crosswalk and asks the harder question: is there a real, functioning operational process behind this? If not, what would one look like, and what's missing?

The two tools share a common model. A gap identified in Nexus translates directly into design work in Mechanic. A mechanism built in Mechanic produces evidence that feeds back into the crosswalk. This connection is structural, not cosmetic — the whole point of using both tools is that the link between regulatory obligation and operational reality becomes explicit and traceable.

Who it's for

Balcony is built for practitioners: the engineers, lawyers, data scientists, and risk analysts who are responsible for making AI governance actually function. It assumes domain literacy — you will encounter terms like controls, mechanisms, artefacts, and crosswalks used with specific meanings — but the product is designed so that people from different disciplines can work in the same tool without translation loss.

Why mechanisms matter

Most governance documentation describes what an organisation should do. Mechanic asks what it actually does, and whether the difference is accounted for. The gap between policy intent and operational reality is where compliance failures happen. Balcony is designed to make that gap visible early, before it becomes a problem.

This approach comes directly from the methodology taught by AI Career Pro, the company that built Balcony. The product is the software expression of that method — which means it is built by people who teach this material, not by a generic GRC vendor looking for market adjacency.

What to read next

• Core concepts — the vocabulary and structure you will use throughout both tools.
• Your first walkthrough — create a board, load an artefact, and see your first Gap.
• Using Nexus — detailed guide to the crosswalk and mapping workflow.
• Using Mechanic — detailed guide to mechanism design and assessment.