One opportunity, carried through the whole system

Relationships — the record, reconciled

The scattered sources become one reviewed record: the organization, the people, the relationship owner inside Harborview, the source of the introduction, and the last verified touch — each fact carrying where it came from. Duplicates are merged with the merge documented, not silent. The record is complete enough that a colleague could pick it up cold.

Pipeline — an owner and a next action

The record sits in a stage that means something, with a named owner and one concrete next action with a date. If the date passes, the record surfaces in the stale queue instead of quietly dying — follow-up stops depending on anyone's memory, which is the entire point of the framework.

Weekly Review — the operating rhythm

Once a week the firm sees the whole board the same way: what moved, what stalled, what is overdue, and what needs a decision. The weekly operating report is generated from the same records — not assembled by hand on Friday afternoon.

Owner — their whole company

Harborview's owner sees every record in their company: the full pipeline, the Vault, the audits, and the cost ledger. It is their company; the view matches the ownership.

Employee — a role slice

An employee sees the records their role works: their own relationships, their next actions, the Vault material their role is approved for. Not the whole pipeline, not the ledger, not other teams' records.

Parent firm — aggregate only

The parent sees Harborview as counts and status: records by stage, stale count, audit status, framework version. No names, no record detail — unless Harborview's owner grants it, explicitly and on the record. This is the no-pooling rule doing its job.