Lifecycle Graph

Business Summary: The Lifecycle Graph is your organization's unified operating memory — domain context, curated wiki documents, agent execution, and governance lineage in one graph that grows from sign-up and powers Perception queries across Nimbus.

Open Lifecycle Graph from the sidebar (Knowledge section). Company Wiki is the document vault view of the same graph — not a separate product.

On this page

• Start here — task guides
• What is the Lifecycle Graph?
• Graph views in the product
• How the graph grows
• Navigating the graph
• Company Wiki and vaults
• Node details and lineage
• Health indicators
• Example scenario
• FAQs

How this fits in Nimbus

flowchart LR
  LG[Lifecycle Graph]
  Perception[Perception orb]
  Overview[Overview Ask Nimbus]
  Audit[Audit and History]
  Agents[Agents]

  LG --> Perception
  LG --> Overview
  LG --> Agents
  Audit -->|View Lineage| LG

Connectors feed live data; wiki vaults and onboarding seed domain context; governed runs add execution and governance nodes. Ask Nimbus and the Perception orb query the Lifecycle Graph without opening the canvas.

Start here {#start-here}

More reference (on this page)

Deep dives live below as anchored sections — not separate sidebar articles:

What is the Lifecycle Graph? {#what-is-the-lifecycle-graph}

Every time you complete onboarding, sync a wiki document, run an agent, approve an output, or connect a data source, Nimbus records what your organization knows and did — and how those records connect. That accumulated graph is your operating memory — not chat history, but a durable map of domain context, institutional knowledge, and governed work.

The Lifecycle Graph is how you browse that memory in the product. It presents your organization as a tree (execution lineage), a network (domain relationships), and wiki vaults (curated documents) — all one graph.

Nimbus treats committed governed work similarly to how engineering teams treat Git: each approved outcome can be committed into an operating ledger with a full decision trace.

Hub sections in the tree view

You also see pieces of operating memory elsewhere — Workstream Activity, Agent outputs, and Audit & History. The Lifecycle Graph brings those threads together in one navigable surface.

Graph views in the product {#graph-views-in-the-product}

The sidebar may show Lifecycle Graph and Company Wiki — both are views of the same operating memory:

flowchart TB
  Memory[Operating memory]
  Tree[Tree view]
  Network[Network view]
  Wiki[Company Wiki vaults]

  Memory --> Tree
  Memory --> Network
  Memory --> Wiki

See Graph views in the product for when to use each canvas.

How the graph grows {#how-the-graph-grows}

The Lifecycle Graph grows as your organization uses Nimbus. A timeline scrubber lets you slide between stages 1 and 8 to see how the tree looked at earlier adoption points.

flowchart LR
  S1[1 Domain context]
  S2[2 Agent activation]
  S3[3 Workstreams]
  S4[4 Execution]
  S5[5 Connectors]
  S6[6 Ontology linkage]
  S7[7 Governance]
  S8[8 Full lifecycle]

  S1 --> S2 --> S3 --> S4 --> S5 --> S6 --> S7 --> S8

See How the graph grows for the full stage reference.

Navigating the graph {#navigating-the-graph}

The tree view is a hierarchy with your organization at the root. Branches extend through hub sections into individual nodes.

See Navigating the graph.

Company Wiki and vaults {#company-wiki-and-vaults}

The Company Wiki is the document layer of operating memory — policies and connector-synced files that agents index during runs. Wiki documentation lives in its own section:

→ Company Wiki — overview, adding content, browse and search

The Lifecycle Graph shows the same vaults in tree and network views alongside execution lineage.

Node details and lineage {#node-details-and-lineage}

View Lineage from Audit & History jumps to related Lifecycle Graph nodes. See Node details and lineage.

Health indicators {#health-indicators}

Hub health chips and the Health tab surface domain and operational readiness. See Health indicators.

Example scenario

A strategy lead confirms product nodes on the Lifecycle Graph network canvas, checks the expense policy in Company Wiki, then traces prior forecast runs on the tree view — one graph, multiple lenses. She asks Perception Which approvals touched this market segment? without opening either canvas.

FAQs {#faqs}

Q: Is the Company Wiki separate from the Lifecycle Graph? A: No. Wiki vaults are nodes in the same operating memory graph.

Q: When does the graph start building? A: Immediately on sign-up — Nimbus seeds domain context from your website and model-assisted enrichment, then expands as you add team members, connectors, workstreams, and governed runs. No manual graph construction is required.

Q: Does the graph build itself? A: Yes. Wiki sync, connector activity, workstream creation, agent runs, and approvals all add nodes and edges in the background. You browse the result in Lifecycle Graph or query it through Perception.

Q: How do I query the graph without opening it? A: Use Ask Nimbus on Overview or the Perception orb.

Q: Where does Audit connect? A: View Lineage on Audit events opens related Lifecycle Graph nodes.

Q: Is operating memory the same as chat history? A: No. Operating memory is durable — runs, deliverables, approvals, wiki vaults, and governance states. Workstream chat is private per user; only governed outcomes feed the graph.