Build the Aurora AV-7 in Daedelus Factory

How this guide works

The suite is a fleet of modules you reach from the Bridge (the launcher). This guide teaches each one as a set of numbered steps, plus little animated walkthroughs that show exactly where to move the mouse and click. Watch the pointer in the frames below — it moves, clicks (you'll see a ripple), switches tabs and zooms, just like you will.

The Aurora AV-7 — our worked example

Before the modules, meet the product. The Aurora is a modular assembly: a tree of parts, from the whole ship down to individual bricks. The suite mirrors exactly this structure.

The assembly, as a build

The same tree, the way the suite stores it

Read the map above and keep it in mind — Vehicle → System → Subsystem → Equipment is the backbone every module hangs data on: requirements attach to levels, kits build subassemblies, drawings describe parts, hardware serialises the physical bricks.

Getting started · the Bridge

Everything begins at the Bridge — the grid launcher in the top-left. Modules are grouped into sections (Personal, Program, Production, Finance, Administration). Click a tile to open a module.

1. Sign in and pick your active project (e.g. MF — Aurora AV-7 Programme). Everything you create belongs to it.
2. Open the Bridge (grid icon, top-left). Hover a section header to jump; click any tile to open the module.
3. Inside a module, use the tab bar under the banner to switch views. Your browser ← back button always works.
4. Note the reference on everything you make — AV-REQ-001, AV-KIT-HULL — it's how items are cited and linked everywhere.
5. Copy the browser URL at any moment to share exactly what you're looking at.

Requirements Nexus AURORA THREAD

Where you capture what the Aurora must do and how each part must be built — and trace one to the other. The module has a top tab to switch between Design (Qualification) and Functional (Acceptance) requirements, or view Both.

Capture a requirement

1. Open Requirements Nexus. Choose the top tab: Design · Qualification for "how a part is built", Functional · Acceptance for "what the ship does".
2. Click + Req. Give it a level (Vehicle / System / Subsystem / Equipment) — e.g. the main drive is Equipment.
3. Write the shall-statement: "The main drive shall achieve 0.5 past lightspeed." Pick the Class (Design or Functional) and a workflow status.
4. Save. It gets a reference like AV-REQ-001 and appears in the left list and the lattice graph.

Link a design requirement to its acceptance test

1. Double-click a requirement to open its focus panel: its linked specification sits above it.
2. A Design requirement shows its Functional counterpart to the right; a Functional one shows its Design counterpart to the left.
3. Click Link counterpart and pick the opposite-class requirement (e.g. link design AV-REQ-001 to acceptance AV-ACC-001).
4. Below the requirement, a tree shows every linked document, waiver, deviation and NC — the whole evidence trail in one place.

Design · CAD viewer AURORA THREAD

Open and inspect the Aurora's 3D models and 2D drawings right in the browser — no CAD install. It accepts a huge range of files: STEP (.stp/.step), IGES, STL, OBJ, glTF/GLB, 3MF, and 2D drawings as DXF and SVG, among many others.

Open a model or drawing

1. Open Design and drag a file onto the viewer, or attach it to a hardware item and open it from there.
2. 3D solids (STEP/.stp, IGES, BREP) tessellate in-browser; meshes (STL, OBJ, glTF, 3MF…) load directly.
3. 2D drawings — export the Aurora hull plate as DXF or SVG and it renders as line work.
4. Orbit (drag), pan (right-drag), zoom (scroll). Press W to cycle display modes: shaded → edges → wireframe → zebra.

Inspect & evaluate

1. Open Model statistics for size, triangles, surface area, volume and centre of mass.
2. Use the Evaluate tools: section plane, wall-thickness, draft, undercuts, curvature and zebra stripes to judge the surface.
3. Measure: tap two points for a distance; a third reads the angle. Explode an assembly to see sub-parts.
4. Link the part to hardware so the model is one click from its requirement, kit and serial history.

Production · Kits AURORA THREAD

A kit is a bill of the bricks (parts) needed to build a subassembly — the way a kit of parts is bagged. Production plans, picks and builds those kits.

Build a kit for the cockpit

1. Open Production and create a kit named for the subassembly, e.g. AV-KIT-CKPT.
2. Add the parts (bricks) and quantities — the kit's bill of materials.
3. Link the kit to its hardware item (Cockpit) and the requirements it satisfies.
4. When stock is ready, run a kit build: pick the parts, record the build, and the assembly moves forward.

Documents AURORA THREAD

Author, compute, revise and sign controlled documents — like the Aurora's assembly manual or its qualification report — with live values, charts and a revision history.

1. Open Documents and click + New. Pick a template (technical note, report, procedure).
2. Write sections; insert compute blocks and tables whose values recalculate live (e.g. total brick count across kits).
3. Insert charts and figures; cross-reference requirements by their AV-REQ-… reference.
4. Release a revision to freeze its computed values, then sign it. Distribute via the distribution list.
5. Link the document to the requirement, kit or milestone it supports — it appears in their evidence trees.

Hardware Management AURORA THREAD

The physical side: serialise the real bricks and assemblies, track their location and status, and keep their full history from intake to shipment.

1. Open Hardware Management and intake a part — give it a serial, material and location.
2. Move it through statuses (received → in build → inspected → installed) — every change is logged.
3. Link the hardware item to its drawing, kit, requirement and any NCs.
4. Print a QR label; scanning it with QR Scan resolves the exact item and its current revision.

Quality AURORA THREAD

When a brick is wrong — a warped hull plate, a mispainted cockpit — you raise a non-conformance (NC). Quality is the corrective-action layer over those NCs: a 4-column Kanban board (open → investigating → corrective action → closed) — drag a card to change its status — with severity, SLA overdue flags, corrective actions and a Metrics dialog, and every finding tied back to the part and requirement it affects.

Raise and work a non-conformance

1. Open Quality and click New NC — the card lands in the Open column.
2. Describe the defect, set the severity (minor / major / critical — it drives the SLA clock) and link the affected part (hardware item) and the requirement or drawing it breaks — e.g. AV-DRW-014.
3. Drag the card across the board as work progresses: open → investigating → corrective action → closed.
4. Open the card's drawer to add corrective actions (+ Add) with owners and due dates; Mark verified when each is proven done.
5. Close the NC when the corrective actions are complete; it stays in the history and the SLA compliance stats.

SLA & metrics

1. Every open NC carries an SLA target derived from its severity — cards past it show an OVERDUE pill.
2. Click ⊞ Metrics for NC counts by status and severity plus SLA compliance of closed NCs; Copy CSV exports the data.

Configuration AURORA THREAD

Configuration keeps the Aurora's design under control: it freezes a baseline of requirements and drawings at each review phase, so everyone builds to the same agreed definition and changes are deliberate.

1. Open Configuration and choose the review phase (e.g. PDR, CDR).
2. Review the candidate baseline: the set of requirements and drawings as they stand now.
3. Click Freeze baseline — the items become read-only snapshots tied to that phase.
4. After freezing, changes go through change control; the next baseline shows what moved since the last one.

Gantt AURORA THREAD

Schedule the build. Gantt lays out the tasks to assemble the Aurora as bars on a timeline, with dependencies (you can't fit the cockpit before the hull) and milestones.

1. Open Gantt. Add tasks for each build step (build hull kit, fit cockpit, mount engines…).
2. Set durations and dependencies — "fit cockpit" starts after "build hull kit" finishes.
3. Drop milestones (diamonds) like Roll-out; link them to contract milestones.
4. Drag bars to reschedule; the timeline reflows dependencies. Assign owners from the directory.

Milestone Management AURORA THREAD

The contractual heartbeats of the programme: payment and review milestones, their benchmarks, and the freeze that captures where the schedule stood at each checkpoint.

1. Open Milestone Management and add the contract milestones (PDR, CDR, Roll-out, Delivery).
2. Give each a benchmark date and criteria; link the requirements or deliverables that gate it.
3. Freeze a milestone benchmark to record the plan at that moment for later variance analysis.
4. Track status as milestones are met; link to Gantt so schedule and contract stay aligned.

Dashboards AURORA THREAD

Build a live wall of widgets over any module's data — requirement status, NC counts, kit-build progress — to watch the Aurora programme at a glance.

1. Open Dashboards and click New dashboard (or start one from a requirement scope in Requirements Nexus).
2. Add widgets: pick a metric (requirement status, V&V coverage, NC count…), a chart type and a scope (vehicle, spec).
3. Add a Roadmap widget for an advanced flowchart pinned to the board: click or drag shapes onto the light-grey snap grid, move and resize them from the corner grip (both snap to the grid), connect them, set colours and due/accomplished dates — every shape is a referenceable RM-### item you can link to any document or item, and hovering a shape fans its linked items out graphically.
4. Arrange the grid; each widget recomputes from live data.
5. Set sharing (view/edit lists) and copy the dashboard URL to share the board.

EAC — Estimate at Completion AURORA THREAD

What will the Aurora actually cost and take to finish? EAC breaks the build into work packages (hull, cockpit, propulsion…), each with a planned budget, and tracks booked vs planned as work burns down.

1. Open EAC and create work packages for the build (WP-HULL, WP-CKPT, WP-PROP…), each with a planned budget and dates.
2. People book time against them in Time Booking; the burn-down updates automatically.
3. Maintain the estimate to complete; the module rolls it into an estimate at completion.
4. Compare planned vs booked per package, person and team to spot overruns early.

Financial Controller AURORA THREAD

The controller runs the programme by control periods: at the end of each period it freezes time, EAC and risks/opportunities so the numbers can't shift under a report.

1. Open Financial Controller and review the current control period.
2. Check time bookings and EAC are complete, then click Freeze period.
3. Frozen time/EAC/R&O become read-only; freeze-compare views show movement since the last period.
4. Reopen a period only to correct — otherwise adjustments belong to the current open period.

Cost Run AURORA THREAD

Model what the Aurora costs under different assumptions. A cost run rolls up part, kit and labour costs into a total you can compare across scenarios.

1. Open Cost Run and create a run for the Aurora build.
2. Pull in kit and part costs and labour from work packages.
3. Create a second scenario (e.g. cheaper hull bricks) and compare the roll-ups side by side.
4. Link the chosen run to the contract and EAC so the cost basis is traceable.

ERP AURORA THREAD

The books and the stockroom: general ledger, inventory of bricks, procurement of parts you don't make, and financial statements — the enterprise backbone under the programme.

1. Open ERP. On Inventory, track brick stock and locations; reorder points flag low stock.
2. On Procurement, raise orders for bought-in parts (e.g. the dish antenna) and match receipts.
3. The General Ledger records costs; Statements roll them into P&L / balance views.
4. Inventory links to Hardware Management, so a serialised brick and its stock record stay in sync.

Contractual Overview AURORA THREAD

The customer picture: the contract to deliver the Aurora, its milestones and value, and how delivery is tracking against it.

1. Open Contractual Overview and open the Aurora delivery contract.
2. Review its milestones and values; these link to Milestone Management and Gantt.
3. Track delivery status and payment milestones against plan.
4. Link contract milestones to the requirements/deliverables that gate them.

Contractual Execution AURORA THREAD

Turning the contract into work: statements of work (SOWs), their execution steps, and the deliverables you hand over.

1. Open Contractual Execution and open the SOW under the Aurora contract.
2. Work through its execution steps, marking each complete as the build progresses.
3. Attach deliverables (the signed assembly manual, the flight-test report) to their steps.
4. Link steps to Gantt tasks and milestones so contract and schedule move together.

Vehicle Overview AURORA THREAD

The product tree at a glance: the whole Aurora from ship down to equipment, with each level's requirements, kits and hardware one click away.

1. Open Vehicle Overview to see the Aurora's product tree.
2. Expand a system (Hull, Propulsion…) to reveal its subsystems and equipment.
3. Each node shows counts (requirements, kits) — click through to that item in its module.
4. Use it as the map of the build: everything hangs off this tree.

Team Execution AURORA THREAD

The team's task board: who is building what, task status and throughput across the Aurora programme.

1. Open Team Execution and create tasks for build activities; assign owners from the directory.
2. Move tasks across statuses (to-do → in progress → done); the throughput strip shows the flow.
3. Link a task to its requirement, kit or Gantt bar so work traces to the plan.
4. Filter by person or team to see individual workloads.

Risk & Opportunities AURORA THREAD

The risk register: what could go wrong (or right) on the Aurora build, scored by likelihood and impact, with mitigations.

1. Open Risk & Opportunities and add a risk (or opportunity) with a description.
2. Score likelihood and impact; the matrix places it and colours the severity.
3. Add mitigations and owners; re-score as they take effect to show the risk moving down.
4. Link risks to the requirement, milestone or work package they threaten.

Hive Mind AURORA THREAD

The team's shared knowledge graph: lessons, decisions and know-how about the Aurora, connected so answers surface across the programme (distinct from your private Second Brain).

1. Open Hive Mind and add a knowledge node — a lesson learned, a decision, a how-we-did-it.
2. Connect it to related nodes and to work items (a requirement, an NC) so context travels with it.
3. Browse the graph or search; shared knowledge is visible to the team.
4. Keep private notes in Home ▸ Second Brain instead — the Hive Mind is deliberately shared.

Portfolio Management AURORA THREAD

Zoom out from one ship to the whole fleet: several Aurora variants (or unrelated programmes) side by side, with status and health roll-ups across projects.

1. Open Portfolio Management to see all projects you can access as a portfolio.
2. Compare status, schedule and risk health across programmes.
3. Drill into any project to switch context to it.
4. Use it (with Projects) to plan cross-programme work.

Projects AURORA THREAD

Create and manage projects, and move items between them — copy a proven kit or live-clone a requirement from one Aurora build into the next.

1. Open Projects to create a new project or switch the active one.
2. Copy an item from another project into yours for a one-off reuse.
3. Live-clone to keep it in sync with the source until you unlink it.
4. Set cross-project links to relate items without moving them.

Cupola View AURORA THREAD

Your window onto live views and embedded streams — a shop-floor camera on the Aurora build, an external dashboard, a live feed — pinned where the team can watch.

1. Open Cupola View and add a view (a stream URL or an embeddable dashboard).
2. Arrange the panes; each refreshes live.
3. Share the Cupola URL so the team watches the same feeds.

Home & Second Brain AURORA THREAD

Your personal dashboard: bookmarks, notepads and a private Second Brain reference library that only you can see — the place to keep your own notes about the Aurora build.

1. Open Home for your bookmarks and quick links to items you use often.
2. Jot working notes in a notepad; they stay private to you.
3. Keep references and clippings in your Second Brain — never shown in Hive Mind or others' views.
4. Pin frequently-used modules and items for one-click access.

Virtual Office AURORA THREAD

Meet, message and collaborate without leaving the suite: rooms, calls, chat and presence — plus temporary rooms and file sharing for people outside the organisation.

1. Open Virtual Office to see who's online (presence) and your rooms and conversations; Members lists the whole office.
2. Click Meeting room to start or join a call; share your screen for a design review of the Aurora model (Devices picks camera/mic, Pop out floats the call).
3. Chat one-to-one or in a channel; mention people, react and pin messages.
4. For an external reviewer, create a temporary meeting room from Meeting room — they join by link + password with a lightweight name/email sign-in.

File Transfer AURORA THREAD

Send and receive large files with resumable uploads, whole folders, and password-protected external share links — the way big models and reports move.

1. Open File Transfer and click New share — pick the direction (send files out, or receive files in), a password and an expiry.
2. Large uploads resume automatically if the connection drops — leave the tab open.
3. Copy link / Copy password / Copy email invite from the share card; the guest opens the link, signs in with name/email, enters the password.
4. To receive, create a receive share — the contact uploads straight into it; Revoke ends a share at any time.

Time Booking AURORA THREAD

Your chronograph: clock in/out, record absence, and allocate your time to EAC work packages so the Aurora's burn-down reflects reality.

1. Open Time Booking ▸ My Time and clock in/out (or enter times directly).
2. On Allocation, assign booked time to work packages — suggestions come from your tasks.
3. Record absence on its tab.
4. The Burn-down compares planned vs booked; allocation locks when the period is frozen.

Badge AURORA THREAD

Your signed identity in the suite: a digital ID with wallet passes and the canteen account — the credential the shop floor and QR flows recognise.

1. Open My Badge (top-right) to see your signed ID and role.
2. Add it to your phone wallet as a pass for quick presentation.
3. Check your canteen balance and history.
4. Your badge identity signs actions across the suite (e.g. document signing).

QR Scan AURORA THREAD

Point your camera at any item's QR label to resolve it instantly, verify it's genuine, and check whether your copy is the current revision.

1. Open QR Scan and allow camera access; point it at an item's QR label.
2. It resolves the exact item and opens it — no typing a reference.
3. It verifies authenticity and flags if your physical copy is an out-of-date revision.
4. Print QR labels from an item's detail pane (look for the QR action).

Organisation AURORA THREAD

The chain of command: people, org charts, task forces and customer/supplier counterpart mappings — the directory every people-picker in the suite reads.

1. Open Organisation and add people with their role and organisation; build the org chart.
2. Define task forces for cross-org groups (e.g. the Aurora build crew).
3. Map counterparts — your contacts to the customer's — for contract work.
4. Everyone here appears in assignment pickers across modules, scoped to the project.

Training & Competence AURORA THREAD

Skills and certificates: competency profiles, training records with expiry tracking, personal plans and the training catalogues — so the right qualified people build the Aurora.

1. Open Training and build a person's competency profile; gaps against their roles show up.
2. Record certificates with issue/expiry; expiring ones are flagged for renewal.
3. Add courses from the catalogue to a personal training plan with target dates.
4. Link a certificate to the requirement it satisfies (a qualification a task needs).

Export Control AURORA THREAD

Jurisdiction, classification and licences: mark controlled items, record the licences that permit their transfer, and keep the compliance trail — because a main drive isn't shipping without paperwork.

1. Open Export Control and set the classification and jurisdiction of controlled items.
2. Record the licences that authorise transfer, with scope and expiry.
3. Check an item's control status before sharing or shipping it.
4. The compliance trail links to the hardware, document or requirement it governs.

Archive AURORA THREAD

The Knowledge Vault — the organisation-wide repository of knowledge across five tabs: Library (documents, textbooks, articles, standards, guides, reports — searchable, kind-filtered, each with an attached file or external link), Personal Library (everything YOU bookmarked — the same bookmarks surface in your Second Brain on the Home deck), Published Papers (papers by people working for the organisation, org authors linking to their Organisation profile), Governance (quick links to the documents that govern the organisation) and Requests (asking publishers / institutions for resources, with a requested → approved → ordered → received pipeline).

1. On Library, click Add material to shelve a document, textbook, article, standard, guide or report — attach a file or an external link. Search and the kind-filter chips narrow the shelf.
2. Bookmark any library item or paper — it lands in your Personal Library tab and in your Second Brain on the Home deck.
3. On Published Papers, Add paper records a publication; organisation authors link to their contact profile in Organisation.
4. On Governance, Add quick link pins the documents that govern the organisation (e.g. the Business Management Guide) — each opens a library item, a controlled document or a URL.
5. On Requests, New request asks a publisher/institution for a resource; advance it with Mark approved / ordered / received, then Add to library shelves the received item.

Admin AURORA THREAD

The command deck (super/admin only): users and roles, organisations, access requests, the audit log, data export, the permission matrix, app settings, reference counters, migration tools, the Tenancy console that shapes which modules each project sees, and the Compliance tab.

1. Open Admin ▸ manage the user whitelist and assign roles; group users into organisations.
2. Decide access requests; the Matrix shows who can do what per module.
3. On Tenancy, set the project's operating mode and org size tier, and activate/hide/archive modules — additive and reversible.
4. Review the audit log (who changed what, when) and export data as needed.

CORE BUSINESS CORE

The organisation's own backbone — everything that is true of the business rather than of one programme: the service desk, incidents, people, time, sites, suppliers, customers, treasury and the regulatory calendar.

How you actually use it

1. CORE is a deck. Each tile opens its own module, and every one of them is tenant-level: the data does not re-scope when you switch project.
2. Reach it from the Bridge, or from the tenant column of the project selector — you do not need a project open to ask an organisation-level question.
3. Access needs main-tenant membership. A partner invited to one programme does not see the group's suppliers or people.

IT Tickets SERVICE DESK

One queue for IT faults, hardware requests and access questions across the whole organisation.

How you actually use it

1. Raise a ticket with what you expected, what happened and when it started — a ticket that says only "it is broken" costs a round trip before anyone can start.
2. Priority orders the queue. A queue where everything is urgent has no priorities.
3. Resolve with what actually fixed it. The next person with the same fault is why the note exists.

Incident Reporting INCIDENT DESK

Safety, security, environmental and quality incidents at organisation level — separate from project compliance because the duty to act does not stop at a project boundary.

How you actually use it

1. Report when it happens, not when it is understood. A late report is the thing regulators ask about.
2. Facts first: what, where, when, who was affected. Cause and corrective action are separate fields because they are separate things — only the second one changes anything.
3. Near misses are worth reporting precisely because nothing happened. It is the cheapest hazard evidence you will get.

Time & Accounts CHRONO LEDGER

Booked hours rolled up across every project, plus the special time account — overtime in, time off in lieu out.

How you actually use it

1. The cross-project total is the number no single project can show you, and the only place over-commitment is visible: each programme's own view looks reasonable on its own.
2. Hours arrive from Time Booking. This is not a second place to enter them.
3. Every time-account movement carries a reason. A balance nobody can explain is a dispute waiting to happen.

HR PEOPLE OPS

People by site and employer: contracts, absences against the site's own working calendar, and offboarding that closes access when the contract ends.

How you actually use it

1. A person has a legal entity (who employs them) and a site (where they work). In a group those genuinely differ.
2. Absence counts WORKING days against the site calendar, so a plant shutdown does not eat somebody's leave.
3. Offboarding closes access as part of the process. An account that outlives its contract is the most common audit finding there is.

Company Pension PROVISION DESK

The company pension scheme — contributions, employer match and statements.

How you actually use it

1. Deliberately a stub today: the screen says what it will hold rather than showing a zero that looks like an answer.
2. Tenant-level, like the rest of CORE — a scheme belongs to the employing entities, not to a project.

Treasury & FX EXCHEQUER

Dated exchange rates against the reporting currency, and the group's open contract value converted at them.

How you actually use it

1. Rates are held WITH THEIR DATE. A single current rate cannot value last quarter's contract, and re-valuing history makes every prior report unreproducible.
2. Exposure spans every project, because currency risk is a group question that each project's view is too small to see.
3. Contracts in a currency with no rate are named rather than converted at a guess.

Supplier Master SUPPLY REGISTER

Every supplier the group buys from, once: origin, category, which sites may use them, and what the last restricted-party screening means today.

How you actually use it

1. A supplier used by three plants is ONE record with three sites allowed. Duplicates are how a group screens a supplier at one site and not another.
2. Screening is recorded with its date, because a clear screening from two years ago is not a clear screening.
3. ERP procurement holds the transactions; this holds who they are and whether we may deal with them.

Customer Accounts ACCOUNT REGISTER

Every customer across every project: invoiced, open, overdue, quoted, credit headroom, and when anybody last spoke to them.

How you actually use it

1. A customer buying from two programmes appears once, with both counted. Each project's view shows part of the relationship and none of the risk.
2. Credit headroom is the number to check before promising more work, not after.
3. "Needs attention" is a worklist: overdue, no headroom, or no recent contact. A quiet account is not a healthy one, it is an unknown one.

Regulatory Calendar STATUTE WATCH

What is due, where, by when and who owns it — statutory filings, notifications, reviews and audits per legal entity.

How you actually use it

1. An obligation belongs to a LEGAL ENTITY. Two entities in two countries do not share a deadline, and a calendar that pretends they do will miss one.
2. Mark it done and the cadence schedules the next one. That is the difference between a calendar and a list.
3. An obligation with no named owner is an obligation nobody will do.

Sites & Maps SITE ATLAS

Plants, warehouses and offices, the legal entities behind them, and the working calendar of each — the physical footprint of the tenant.

How you actually use it

1. Most of the suite's date arithmetic starts here: HR absence and production planning both read the site calendar.
2. Sites are what scoped access is expressed in — "editor in the Puebla plant, viewer elsewhere" is only sayable because sites are records.
3. If a duration looks wrong anywhere in the suite, check the site calendar first.

Glossary COMMON TONGUE

The organisation's abbreviation list: every abbreviation the suite uses and every meaning it has here. It is exactly what the hover shows when you rest on an abbreviation anywhere in the tool.

How you actually use it

1. Search by abbreviation, by what it stands for, or by domain; the domain chips narrow the list.
2. The same letters may mean several things — CC is a cost centre in the ledger and a copied-in recipient in mail. Add each meaning as its own entry; the hover lists them all.
3. Switch off a built-in meaning that does not apply in this organisation; it can be switched back on. The list also appears under Archive ▸ Glossary.

Organisation Settings TENANT COMMAND

Deployment-wide identity and the standards every project inherits — a deck whose tiles each own one part of the answer.

How you actually use it

1. Work it in order: Type sets the maturity profile, Structure declares the wiring, Chart draws it, Rights sets the ladder, Approvals sets who signs, Templates holds the document standards.
2. Identity set here appears on documents and exports everywhere. A cover naming a different organisation per programme is a document nobody can send.
3. Defaults are inherited going forward; work already issued keeps the standard it was issued under.

Company Templates TEMPLATE FORGE

The document cover template, the company disclaimer and the export-control raters every project inherits.

How you actually use it

1. Changing a template changes what NEW documents inherit. Issued documents keep theirs, because an issued document must stay reproducible.
2. The disclaimer lives here rather than per project: legal text that differs by programme is legal text nobody has reviewed.
3. Export-control raters are organisation-level because a classification scheme that varies by project is not a scheme.

User Rights & Hierarchy RIGHTS GRID

The ladder and what each rung may do: hierarchy levels, assignments, delegation of authority and the global access roles.

How you actually use it

1. Delegation records the LIMIT as well as the person. Authority without a bound is substitution, not delegation.
2. Global roles cut across every project. They are powerful by design, which is the reason to grant few — and to review the list, because it only grows unless somebody looks.
3. The ladder is authority; the org chart is structure. A senior engineer is high on one and deep in the other.

Organisation Type MATURITY PROFILE

Classify the tenant from startup to enterprise — the profile that scales what the rest of the suite recommends.

How you actually use it

1. Pick it honestly. Claiming "enterprise" produces governance advice nobody will follow, and advice nobody follows is worse than none.
2. Nothing is locked out by the profile; it scales recommendations and defaults.
3. The gap between the claimed profile and the readiness score is the useful number — it is the work.

Organisation Structure STRUCTURE BLUEPRINT

How the company is wired — Functional, Divisional, Matrix, Project-based or Hybrid — and the unit tree that structure produces.

How you actually use it

1. Describe reporting reality, not the drawing somebody would like. A matrix declared as functional will not explain why two people own the same decision.
2. For matrix and hybrid, name the DOMINANT AXIS. A matrix with no tie-breaker is how a decision stalls for a fortnight.
3. Each unit has a lead; a unit without one is shown, because that is usually an oversight.

Organisation Chart COMMAND ATLAS

The declared organisation drawn: the unit tree with its leads, and the ladder roster of every mapped member.

How you actually use it

1. It is a view, not a second place to define the company — edit Structure or Rights and the chart follows.
2. The gaps are the useful output: people with no unit, units with no lead. A tidy chart usually means an incomplete one.

Approval Flows SANCTION CHAIN

Who may sign each governed action, how many signatures it needs, and whether the chain is staffable with the people you have today.

How you actually use it

1. A rule needing two signatures from a level with one person can never complete. The screen says so before you rely on it.
2. Self-approval is refused by the database, not merely discouraged. A chain the requester can sign is not a control.
3. Re-check staffability after people leave — a chain that worked last quarter may not work now.

Messaging COMMS RELAY

Direct and group chat — the same conversations as the Virtual Office, given the whole window.

How you actually use it

1. One message store, two ways in. Nothing is duplicated and nothing is lost by switching surface.
2. Threads, tags and categories exist so a decision taken in chat can be found again.
3. If you would be annoyed to lose it in three months, it does not belong only in chat — put it in a wiki page, a requirement or a ticket and link back.

CRM RELATIONSHIP DESK

The demand side: priced, versioned quotes to customers ERP already knows, the pipeline behind them, cases, targets and renewals — and the handoff that turns an accepted quote into a receivables invoice.

How you actually use it

1. Quotes price from a PRICE BOOK, which is what makes two quotes comparable. Discounts are allowed and recorded as discounts.
2. A quote is versioned: re-pricing makes a new version rather than overwriting the one the customer holds. The version they accepted is the one that binds.
3. Accepted quotes hand off to ERP receivables — raised from what was accepted, not re-keyed from it.

Values & Comparisons DATUM

A shared registry of named values with units and owners, and live threshold checks against them.

How you actually use it

1. Register once and cite it. A figure copied into four documents is four figures that will disagree within a year.
2. The unit is not optional — an unqualified number is the most expensive kind of shared data.
3. Threshold checks re-answer when the registered value changes, so a new limit does not leave stale conclusions in place.

Project Wiki KNOWLEDGE BASE

The project's written knowledge: pages, structure and the links that connect what is written to what is being built.

How you actually use it

1. A wiki page is where a decision goes to be found again — chat is where it was said.
2. Link pages to the requirements, documents and items they concern; the link is two-way, so the work points back at its reasoning.
3. Structure it for the reader who arrives in six months, not for the person writing today.

AI Gateway MODEL CONTROL

Which agents may read or write what, where the models run, and what they may remember.

How you actually use it

1. Agent credentials CANNOT WRITE. Anything an agent produces waits in an approval queue for a person — a property of the deployment, not a setting to remember.
2. "Where the models run" is the first question a sovereignty assessment asks, and a model outside your jurisdiction is a transfer that needs a basis.
3. Capability accumulates. Review the list, because nothing removes it but a person looking.

AI Agents AGENT ROSTER

The agents themselves — what each one is for, what it has proposed, and what a person did with those proposals.

How you actually use it

1. Every proposal is attributable to the agent that made it and the person who accepted it. That pairing is what makes an AI-assisted change auditable.
2. An agent whose proposals are always rejected is telling you something about its brief, not about the reviewer.
3. Capability is granted in the AI Gateway; this is where you see what was done with it.

Full module index (58)

Every module, what it's for, and where it sits. All 58 modules have a guide section; the core workflow modules additionally carry an interactive walk-through — follow any "Full guide →" link to its section. COMPLETE

Frequently asked questions

Using the in-app Help centre

This written guide is the deep, illustrated companion to the Help centre built into the app. Both cover the same ground; use whichever is closer to hand.

1. Click the ? Help icon in any module's banner.
2. Click ▶ Start live tour for the click-through walkthrough over the REAL module: a spotlight highlights each element, you advance with Next › / ‹ Back at your own pace, and steps that point at a tab really switch the live view under you. Multi-level tours open on a chapter chooser — start at the overview or jump straight to a deeper chapter (the CHAPTERS link in the card brings the chooser back); finishing a chapter offers Next: <chapter> › so one tour flows into the next.
3. You get that module's guide: what it's for, step-by-step how-tos and a module FAQ.
4. Below it, the universal basics (navigation, references, links, sharing) and the global FAQ.
5. Use the search box to find any how-to across every module — results rank the module you're in first.