Skip to main content
A project’s architecture is the blueprint of your app: its parts, what each one is responsible for, how they connect, where data lives, and the decisions behind them. Iron Octopus keeps it as a versioned document. When it plans a feature, it plans against the current published version, so each change fits the app you already have instead of starting from scratch.

​
What it contains

Each version has two forms of the same content:

​
How Iron Octopus uses it

When you describe an idea, Iron Octopus plans it against the project’s current published architecture. It places new work in the right components, respects existing boundaries and decisions, and records which architecture version each plan used.
Today the architecture shapes planning. Publishing a version doesn’t add gates, and code review doesn’t yet check each change against the architecture.

​
Ways to create one

​
Drafts and published versions

An architecture is always either a draft you’re working on, or a published version. Published versions are immutable: to change one, you create a new draft from it, edit it, and publish it as the next version. Only the published version is used for planning. See update and publish a version.

​
Where you see it

Open a project and choose Architecture. The page has tabs for Draft, Guided chat, Library, Versions and Published.

​
On your plan

On Pioneer you can use the managed standards, customize a project’s own copy, and keep reusable personal and workspace templates.