The big picture

Every workspace in GreenVee is organized around five spines — five long chains of related concepts. Almost every screen, every form, and every report in GreenVee is a view onto one of these five spines, or a combination of two of them.

If you remember just this page, you will have the right map in your head for the rest of the docs.

The five spines

Spine A — Work plan (the WBS)
   Portfolio  →  Program  →  Project  →  Segment  →  Task Package  →  Task  →  Subtask

Spine B — The plant (what you are building)
   Project  →  Technical Structure  →  Node  →  Required Goods + Required Specs

Spine C — People and time
   Employee  →  Skill  →  Project Member  →  Planned Hours / Booking  →  Time Entry

Spine D — Money
   Project  →  Budget  →  Cost Item  →  Cost / Benefit / Earning Occurrences  →  Order

Spine E — Materials
   Good Type  →  Good  →  Variant  →  Stock + Movements  →  Procurement Request  →  Usage on a Task

What each spine is for

Spine	Question it answers
A. Work plan	What work needs to happen, in what order, and who is responsible for it?
B. The plant	What physical thing is this project actually building, down to its components and specs?
C. People and time	Who is working on this, with what skills, and how many hours did they spend?
D. Money	What is this project supposed to cost and earn, and what has actually happened?
E. Materials	What goods do we need, where are they, when do we get them, and where are they used?

How the spines connect

The spines are not isolated. They cross at well-defined points:

• Project is the meeting point of Spines A, B, C, and D.
• Task (Spine A) is the place where People (Spine C, via planned hours) and Materials (Spine E, via good usage) are consumed.
• Project Member (Spine C) is the bridge between an Employee and a Project — a task is assigned to a project member, never directly to an employee.
• Good Variant (Spine E) is the bridge between the catalogue and a Node on the Technical Structure (Spine B), via a required good line.
• Order (Spine D) is the sales-side record sitting next to the project, tracking what was sold to the customer.

The project lifecycle

Every project moves through a fixed sequence of phases, in this order: Initial → Definition → Planning → Execution → Closing → Successfully Closed. A project can move to Cancelled from any phase. This phase is the project’s headline status everywhere you see it — the Scoreboard, portfolio lists, reports.

Inside a project

When you open a project, it is organized into 11 tabs: Scoreboard, Profile, Work Board, Resources, Financial Performance, Risks & Chances, Engineering, Procurement, State Reporting, Drive, and Insights. Each tab is mostly a view onto one of the five spines above — Work Board is Spine A, Engineering is Spine B, Resources is Spine C, Financial Performance is Spine D, and Procurement touches Spine E.

Around the spines

A few things in GreenVee live alongside the spines rather than on them:

• Issues — a separate ticket world for state-machine items like approvals, requests, and ad-hoc todos. Distinct from Tasks. (See Day-to-Day Work.)
• Risks, Opportunities, Decisions, State Reports, Key Takeaways — a governance layer attached to projects, programs, and portfolios.
• Drive (files), Channels (messaging) — the collaboration surface.
• Agents, Skills, MCP Servers, Workflows — the AI and automation layer.

The Reference section has a diagram of the five spines and an entity index that points back into these docs.