Projects and Relations

PRIMA CRM

PRIMA CRM connects companies to the projects in your AI Business OS project register. It answers two different questions about a project, with two different records.

Question	Record	What it says
Whose project is this?	Project link	A company is involved in a project, and in what capacity
How does this project connect to that one?	Project relation	One project informs, replaces, overlaps with or sits inside another

Project Links

A link ties a company to a project ID such as P012. Links are many-to-many, so one company can appear on several projects and one project can involve several companies.

Each link can carry three details.

Detail	What it means
Relationship	The company’s role on this project: `client`, `supplier`, `partner`, `internal` or `other`
Department	The department the project sits in
Notes	Free text about the link

The relationship on a link describes this one project. A client can also supply you on one project, and the link records that without changing the company’s overall relationship. Where a company has no relationship of its own, the CRM derives one from its links.

Linking and Unlinking

Tell Claude which company belongs to which project.

Link Harbour Design Studio to P012 as the client.
Northfield Print supplies the printed materials for P012.

Linking a pair that already has a link updates the link’s details. A detail you leave out keeps its current value. Unlinking removes the link and leaves both the company and the project as they were.

To see every company on a project, ask Claude.

Which companies are linked to P012?

Live Project State

A linked project shows its current state on the company profile. The CRM reads these values from the project register each time you ask, so they are always current.

Value	Where it comes from
Name and status	The project’s entry in `.claude/state/state.json`
Task progress	The task counts in the project register, shown as done out of total
Last worked	The project’s last worked date
Latest action	The project’s latest action, read from its detail file in `.claude/state/projects/` when your register uses the split format

Any value the register does not hold shows as a dash. The CRM reads both the older single-file register and the newer split format, and it never writes to the project register.

A Project ID the Register Does Not Know

You can link a company to a project ID that is not in the project register. Claude stores the link and warns you, and the profile shows the project as NOT IN STATE. That makes a mistyped ID visible straight away.

Project Relations

A relation records how one project’s work connects to another’s. Relations cross company boundaries, which is why the CRM keeps them apart from links. A finance system upgrade run by one supplier can shape a CRM replacement run by another.

Relation Types

The CRM stores each relation once, with a direction, and reads it correctly from either end.

Type	From the first project	From the second project	Use when
`informs`	informs	informed by	One project produces knowledge, data or decisions the other depends on
`supersedes`	supersedes	superseded by	A new system or version replaces an old one
`shares-scope`	shares scope with	shares scope with	The work itself overlaps. Direction carries no meaning
`part-of`	part of	contains	A workstream sits inside a larger programme

Relations Describe, the Task Graph Schedules

A relation of type informs records that one project feeds another. It sets no start date and blocks nothing. Scheduling belongs to the task graph in PRIMA Project Management, which owns dependencies between tasks. See Tasks and Dependencies.

Rules

Repeating a relation updates its note. Relating the same two projects with the same type again changes the note and adds nothing new.
Removal follows direction. Removing a relation from P010 to P012 leaves any relation from P012 to P010 in place. Leave out the type to remove every relation from the first project to the second.
A project cannot relate to itself. The CRM rejects the request, and it rejects any type outside the four above.
Unknown project IDs are allowed. The CRM stores the relation, warns you, and shows the project as NOT IN STATE.

A Worked Example

The example below uses an invented workspace. A telecoms company, Brightwater Telecom, does two separate jobs for you. It is integrating a phone system (P011) and supplying a new CRM platform (P010) to replace your old one (P012). A second supplier, Ledgerline, is upgrading your finance system (P013), and its data model decides how the new CRM stores customer records.

First, link each project to the company involved.

Link Brightwater Telecom to P010 and P011 as supplier, and to P012 as internal.
Link Ledgerline to P013 as supplier, department Finance.

Then record how the work connects.

P010 supersedes P012. The new CRM platform replaces the legacy system.
P013 informs P010. The finance data model sets the CRM customer record structure.

The phone system project gets no relation. It sits under the same supplier as the CRM work and has nothing to do with it.

Ask for the relations on one project, and the CRM reads each relation from that project’s side.

# Related Projects — P010

| Relation         | Project | Name           | Status      | Tasks    | Last Worked |
|------------------|---------|----------------|-------------|----------|-------------|
| P010 supersedes  | P012    | Legacy CRM     | paused      | 3/3 done | 2026-05-01  |
| P010 informed by | P013    | Finance System | in-progress | 2/8 done | 2026-08-28  |

## Why These Connect

- **P012** (supersedes): The new CRM platform replaces the legacy system
- **P013** (informed by): The finance data model sets the CRM customer record structure

Ask for the project graph of one company, and the CRM separates relations among its own projects from those reaching projects under other companies.

# Project Graph — Brightwater Telecom

**Linked projects:** P010, P011, P012

## Relations Within This Company

| From | Relation   | To   | Note                                        |
|------|------------|------|---------------------------------------------|
| P010 | supersedes | P012 | The new CRM platform replaces the legacy system |

## Relations Reaching Outside This Company

These connect one of this company's projects to a project linked elsewhere, or to none.

| From | Relation | To   | Note                                                     |
|------|----------|------|----------------------------------------------------------|
| P013 | informs  | P010 | The finance data model sets the CRM customer record structure |

**Standalone:** P011 — linked to the company but not related to any project.

The finance relation appears under “reaching outside” because P013 belongs to Ledgerline. The phone system project appears as standalone, which tells you the lack of a relation is a fact about the work. You also see these relations on the company profile, under “How These Projects Relate”.