People Blueprint — Product Documentation¶

Manager-grade team intelligence: see every person's archetype, how they pair with you, and where your team's friction lives.

Version 1.0 · Last updated April 2026 Route: /people-blueprint · Page: PeopleBlueprintPage.tsx Service: corporateEngine.ts Gate: canAccessCorporate(profile) — requires Discovery + Life Design + paid plan

1. What Is People Blueprint?¶

People Blueprint is the relational intelligence layer of the MindMeditate Personality System.

It answers three questions a manager or collaborator never has structured answers for:

Question	What People Blueprint returns
"How should I work with this one person?"	A per-person compatibility guide with dos/don'ts, approach style, and a growth edge
"How does my team actually function together?"	Team-wide chemistry, coverage gaps, collective strengths and blind spots
"What is the one thing I should do differently as a leader?"	An AI-generated team narrative with one specific recommendation

Unlike Relationship Lens (which compares exactly two people), People Blueprint is N-person and directional — it knows who's your manager, who's your peer, and who reports to you, and the advice is different for each.

2. Where It Sits in the Journey¶

Personality Test  →  Self Mastery  →  Life Design  →  Growth Loop  →  People Blueprint
   (Who)             (Insight)        (Direction)     (Execution)    (Relationships)

Stage	Output
Personality Test	Archetype + Force + Secondary
Self Mastery	Inner pattern + 48-hour commitment
Life Design	Vision, Ikigai, pillars, strategic habits
Growth Loop	Streaks, weekly reflections, sprint reviews
People Blueprint	Per-person guides + team intelligence + AI team coach

People Blueprint is the final stage — it's where everything the user has learned about themselves gets applied to the humans around them.

3. Adding People — Two Paths¶

Every person added is a CorporateRelationship. The user can add them in one of two ways:

The other person has taken the MindMeditate Personality Test and shared their profile link with you.

Paste the /share/:token URL or bare token
The system resolves the linked UID via getShareLink()
Their live archetype + secondary + force is pulled — always in sync with their actual profile
isLinked = true on the resulting CorporateGuideResult

Path B — Manual (Fallback)¶

The other person hasn't taken the test or hasn't shared their profile.

Pick one of the 5 archetypes manually (manualArchetype)
Optionally pick a secondary (manualSecondary)
The system runs the same compatibility engine, but flags the result as isLinked = false

Manual entry is a deliberate escape hatch. It lets a manager map out a whole team even when most reports haven't taken the test — then those reports can be "upgraded" to linked profiles later.

The 5 selectable archetypes with descriptions (from ARCHETYPE_DESCRIPTIONS):

Archetype	Description
Driver	Results-driven, decisive, moves fast — thrives on ownership and winning
Visionary	Ideas-first, inspiring, sees the big picture — energised by possibility
Integrator	People-centred, collaborative, harmony-seeking — the connective tissue of teams
Stabilizer	Process-oriented, reliable, risk-aware — the dependable backbone of execution
Specialist	Deep expertise, quality-focused, domain-driven — masters of their craft

4. The Three Relationship Directions¶

Every relationship is one of three directions. Direction changes the advice.

Direction	Icon	Meaning	Tone of guidance
Manager ⬆️	ArrowUp	This person manages you	How to be managed well by this archetype
Peer ➡️	ArrowRight	You work at the same level	How to collaborate without stepping on each other
Report ⬇️	ArrowDown	This person reports to you	How to lead this archetype effectively

Directional logic is encoded in the DirectionalInsight layer of CorporateGuideResult, which contains 8 direction-specific fields:

Field	Example (Manager direction)
`rapport`	How to build trust with this archetype when they're above you
`influence`	How to advocate for an idea upward to them
`conflictApproach`	How to disagree without wrecking the reporting relationship
`whatTheyValue`	Specific things this archetype values in a direct report
`yourGrowthEdge`	Your biggest growth area in this specific direction
`theirTrigger`	What silently frustrates this archetype in a report
`workflowStyle`	Day-to-day update / collaboration / delegation style
`keyValues`	Top values this direction pulls out of them

The same person, if they moved from being your manager to your peer, would produce a different guide — even though the underlying archetype pairing hasn't changed.

5. The Per-Person Guide¶

For each added person, computeCorporateGuide() returns a full CorporateGuideResult:

Name + direction badge + (if manual) archetype badge
Overall compatibility score (0–100) with colour coding:

Score	Colour	Label
80–100	Emerald	Excellent chemistry
65–79	Indigo	Strong fit
50–64	Amber	Workable with care
0–49	Red	High friction risk

Core compatibility dimensions¶

A set of DimensionBar cards — each is a named axis (Communication, Trust, Pace, Decision-making, etc.) with a 0–100 score and an expandable note.

Green flags / Watch areas¶

Green flags — what will naturally work
Watch areas — where friction shows up
Collaboration tips — concrete ways to lean into the strengths

Dos & Don'ts¶

Two lists: specific behaviours that will help you in this pairing (dosList) and behaviours to avoid (dontsList).

Archetype pair insight¶

A paragraph-length summary of what makes this specific pairing (e.g. Driver × Specialist) distinct — its signature strength and signature friction pattern.

Traits to watch / Conflict flashpoints¶

traitsToWatchOut — behaviours the other person may display under stress that you'll find difficult
conflictFlashpoints — predictable disagreement triggers

Approach guide¶

A set of short prescriptive rules shared with Relationship Lens — how to make first contact, how to frame requests, how to handle disagreement.

For you, personally¶

adviceForYou — one paragraph focused on you, not the other person
growthEdge — the single growth instruction for you in this specific pairing

Directional layer¶

All 8 DirectionalInsight fields rendered as contextual cards (rapport, influence, conflict, triggers, workflow, etc.).

6. Team Intelligence¶

When a manager has added 2 or more reports, computeTeamIntelligence() becomes available, returning a GroupCompatibilityResult.

What the team view shows¶

Field	Meaning
`averageScore`	0–100 overall team compatibility
`overallLabel`	Qualitative label for that score
`collectiveStrength`	What this exact archetype mix is uniquely good at
`collectiveBlindSpot`	What this mix systematically misses
`coverageGaps`	Archetypes missing from the team (e.g. "no Stabilizer — watch for execution gaps")
`pairResults[]`	Every pairwise compatibility score within the team

Highest chemistry / Most friction risk¶

The UI automatically surfaces: - The top pair — the two team members with the highest natural chemistry - The bottom pair — the two most likely to friction

This is often the manager's most actionable insight: "I didn't realise X and Y had the lowest compatibility in the team".

7. The AI Team Coach¶

generateTeamNarrative() calls Gemini with a pre-seeded team dossier and returns a 3-paragraph narrative:

What makes this team naturally strong given the archetype mix
The key risks and friction points this combination creates
One specific, actionable recommendation for this manager

The dossier injected into the prompt includes:

Full team roster (manager + reports, each with archetype)
Average score + overall label
Collective strength + collective blind spot
Coverage gaps
Top pair (highest chemistry)
Bottom pair (most friction)

Beyond the one-off narrative, users can open the AI Team Coach — a live chat built via buildTeamCoachSystemPrompt() that has continuous access to the same team data. It ships with buildTeamSuggestedQuestions() which returns starter questions tailored to the user's archetype, such as:

"Who on my team is likely to push back on my decisions — and why?"
"Which two reports should I pair on the next stretch project?"
"What's the best way for me as a Driver to lead this team?"

8. Data Model¶

People Blueprint writes to profile.corporateData in MongoDB. Key shapes (from corporateEngine.ts):

interface CorporateRelationship {
  id: string;
  relationshipType: 'manager' | 'peer' | 'subordinate';
  name: string;
  linkedUid?: string;        // set when using share-link path
  shareToken?: string;
  manualArchetype?: string;  // fallback: one of the 5 archetypes
  manualSecondary?: string;
  addedAt: string;
}

interface CorporateReportConfig {
  includePersonalityReport: boolean;
  includeLifeDesign: boolean;
  includeGrowthLoop: boolean;
  includeFinancialPlan: boolean;
}

// Computed live (not persisted) — one per added person
interface CorporateGuideResult {
  relationship: CorporateRelationship;
  otherName: string;
  otherArchetype: string;
  isLinked: boolean;           // true = share-link, false = manual
  overallScore: number;        // 0–100
  overallLabel: string;
  dimensions: {...}[];         // DimensionBar inputs
  greenFlags: string[];
  watchAreas: string[];
  collaborationTips: string[];
  dosList: string[];
  dontsList: string[];
  archetypePairInsight: string;
  traitsToWatchOut: string[];
  conflictFlashpoints: string[];
  approachGuide: {...};
  adviceForYou: string;
  growthEdge: string;
  directional: DirectionalInsight;  // 8-field direction-aware layer
}

Archetype name mapping¶

Internally the engine uses detailed archetype names while the UI exposes the 5 user-facing ones. The mapping lives in ARCHETYPE_TO_ENGINE_NAME:

User-facing	Engine-facing
Driver	The Achiever
Visionary	The Visionary
Integrator	The Connector
Stabilizer	The Guardian
Specialist	The Architect

toEngineName() handles the translation so that pair-scoring works identically whether the profile came from a share link or a manual selection.

9. Design Principles¶

Direction changes the advice. Manager / Peer / Report produce different guidance for the same pairing. Role context matters more than raw archetype compatibility.
Manual fallback, not manual-only. A manager can map a whole team in minutes via manual archetypes, then "upgrade" any report to a linked profile later.
Live over cached. Linked profiles pull the other person's current archetype — if they retake the test and their profile shifts, your guide auto-updates.
Team = more than sum of pairs. The collective strength / blind spot / coverage gap layer produces insights no individual pairing reveals.
Top pair + Bottom pair are the most actionable numbers. Managers don't act on averages — they act on outliers.
Narrative, then chat. The one-off 3-paragraph team narrative gives a first read; the AI Team Coach lets the manager interrogate it.
Privacy of manual entries. Adding a manual person does not notify them. Linked profiles only share what the linked user explicitly made shareable.

10. Glossary & FAQ¶

Glossary¶

Relationship — one entry in the user's corporate map: a person + a direction + an archetype source
Direction — manager / peer / subordinate — determines which directional insights load
Linked — archetype pulled live via share link (isLinked: true)
Manual — archetype manually picked (isLinked: false)
Compatibility score — 0–100 composite across all dimensions
Dimensions — axes like Communication, Trust, Pace, Decision-making that compose the overall score
Green flag / Watch area — what will naturally work / where friction shows up
Collective strength / blind spot — emergent property of the team as a whole (not any one pair)
Coverage gap — an archetype missing from the team (signalling a predictable weakness)
Top pair / Bottom pair — highest-chemistry and highest-friction pairs in the team
AI Team Coach — live chat with continuous access to team dossier

FAQ¶

Q: How many people can I add? No hard cap. Performance tested up to ~25 reports. Beyond that, consider segmenting by squad.

Q: Can I move someone from manual to linked later? Yes — delete the manual entry and re-add them via the share link path. Their history is per-relationship so name + direction carry over if you re-enter them.

Q: Does the person I add get notified? No. Adding is silent. Even linked profiles only reveal what the other person has chosen to make shareable.

Q: Why do Manager / Peer / Report produce different advice? Because the same archetype pairing plays out completely differently depending on power direction. A Driver managing a Specialist needs to respect depth; a Driver reporting to a Specialist needs to build patience. Same pair, opposite lesson.

Q: What if I don't know someone's archetype? Use your best guess from the 5-description list. The system will still produce useful advice — and you can refine it later, or invite them to take the test and upgrade to a linked profile.

Q: Why is Team Intelligence only for reports, not all directions? Because most managers have a defined team (reports), and team analysis assumes a single leader + group structure. Peer-group analysis is on the v1.1 roadmap.

Q: Can I export the team report? CorporateReportConfig has flags for including Personality / Life Design / Growth Loop / Financial Plan sections. Export format and sharing are v1.1.

Q: Is People Blueprint the same as Relationship Lens? No — Relationship Lens is a 1:1 tool (you vs one partner). People Blueprint is 1:N with direction + team intelligence. They share the underlying compatibility engine but solve different problems.

Q: How does this respect the other person's privacy? Only via linked profiles, and only what they've marked shareable. Manual entries store only the name and archetype you typed — nothing is fetched from or about that person.

11. Appendix — Compatibility Dimensions & Weightings¶

From RELATIONSHIP_CONFIGS in compatibilityEngine.ts. Every overall compatibility score is a weighted sum of the dimensions for that relationship type. Weights sum to 1.00 per type.

Relationship type	Dimension (weight)	Dimension (weight)	Dimension (weight)	Dimension (weight)
Friendship (`friend`)	Energy Match (0.25)	Openness to Experience (0.25)	Values Alignment (0.30)	Social Orientation (0.20)
Life Partner (`life_partner`)	Core Values Alignment (0.30)	Life Balance Harmony (0.25)	Decision Style Fit (0.25)	Growth Path Alignment (0.20)
Family (`family`)	Communication Style (0.30)	Shared Values (0.25)	Energy Compatibility (0.20)	Lifestyle Structure (0.25)
Team Member (`team_member`)	Work Orientation (0.30)	Work Style (0.25)	Decision Making (0.25)	Drive & Pace (0.20)
Business Partner (`business_partner`)	Role Complementarity (0.30)	Decision Alignment (0.25)	Growth Vision (0.25)	(additional axis as scored)

Key patterns to notice: - Values / role-complementarity always carry 0.30. Across every relationship type, the single heaviest axis is "are we pointed at the same thing?" — whether that's values (personal relationships) or complementary roles (work relationships). - Energy / pace always carries 0.20. Pace matters but doesn't outweigh values — a slow-and-steady and a fast-and-driven pair can still be strong if values and decision style align. - Decision style is 0.25 in every work context. In business and team relationships, how you decide matters almost as much as what you're deciding toward.

Dimension scoring scale¶

Each dimension is scored 0–100 by its dedicated scorer function (energyCompatibility, opennessCompatibility, sharedFocusZones, decisionStyleCompatibility, structureCompatibility, lifeWheelAlignmentScore, selectedPathAlignment, orientationCompatibility). The overall compatibility score is Σ (dimensionScore × weight), also 0–100.

Thresholds used in the note generators: - ≥ 80 — strong complementarity / shared direction - ≥ 75 — naturally compatible - ≥ 65 — workable with some intentional work - < 65 — predictable friction; requires explicit agreements

12. Appendix — 25-Pair Archetype Matrix¶

One-line signature for every archetype × archetype pairing (including same-type). Read as "row archetype relating to column archetype" — the advice reads differently in the other direction because the role differs even when the pair doesn't.

	+ Driver	+ Visionary	+ Integrator	+ Stabilizer	+ Specialist
Driver	Twin engines — fast, aligned, burn out together unless one slows.	Idea plus execution — legendary when roles are clear, combative when not.	Pace plus warmth — willing followership, but the Driver must stop steamrolling.	Velocity plus reliability — best operational pairing, worst when Driver skips the system.	Speed plus depth — elite output, conflict over "ready enough."
Visionary	Invention plus delivery — the classic founder pair; tension when roadmap changes mid-sprint.	Ideation spiral — high inspiration, low completion; one must eventually commit.	Story plus belonging — movement-building, fragile when hard decisions are avoided.	Creativity plus structure — rare and valuable; tension when plan kills spark.	Novelty plus rigour — frontier research pair; works if Specialist tolerates ambiguity.
Integrator	Warmth plus drive — healthy followership, strained when pace overrides care.	Connection plus meaning — culture-shaping pair, drifts without grounding.	Mutual safety — deep trust, risks becoming echo chamber; conflict avoided, not resolved.	Empathy plus order — calm and effective; risks over-accommodating each other.	Relationships plus mastery — mentor-protege dynamic; Specialist feels seen, Integrator feels deepened.
Stabilizer	System plus push — keeps velocity safe; friction when Driver improvises.	Order plus imagination — methodical innovation; Stabilizer must tolerate messy idea phase.	Structure plus care — trusted facilitation; risks absorbing both stress streams.	Twin pillars — ultra-reliable, ultra-slow to change; risk: loyalty to obsolete systems.	Process plus precision — reference-grade output; both rigid under pressure.
Specialist	Depth plus action — rare shipping power; conflict over rigour cuts.	Mastery plus vision — serious R&D pair; risk of endless wander.	Expertise plus translation — teaching-master pair; protects Specialist from isolation.	Craft plus discipline — lifetime-master trajectory; change-averse together.	Twin experts — brilliant 1:1 depth, competitive if scope overlaps.

Reading tip. For a report / subordinate relationship read the matrix diagonally: your archetype is the row, the other person's is the column. For a manager relationship, swap rows and columns — the same pair produces different advice depending on power direction.

📝 Content Backlog (documentation edits only)¶

These are gaps in this .md file. No engineering work — just writing / pulling from existing source files.

[ ] Add screenshots of per-person guide + team intelligence views
[ ] Translate to Bahasa Malaysia

🛠️ Product Roadmap (features to build)¶

These are real engineering investments — not documentation tasks.

[ ] Peer-group analysis — team intelligence for groups without a single leader (not just manager + reports)
[ ] Export team report (PDF / shareable link) per CorporateReportConfig flags
[ ] Bulk-import team via CSV
[ ] Push notification when a linked person's archetype shifts after a re-test

This document describes the production behaviour of PeopleBlueprintPage.tsx and its backing service corporateEngine.ts. When in-product behaviour and this document disagree, the app is the source of truth and this doc should be updated.