Portfolio member · home repo

Lives in its own CI and deploy — not listed in toolbox /api/registry or aggregate /api/health.

DevPlane

Operator control plane scoped to whatever repo on disk you're shipping today.

Character

You're orchestrating PAT cards across clones — toolbox, Performix, meta-factory, Principia — while keeping documentation and mission state from floating away in stray markdown.

Problem

External. Multi-repo work means fragmented context — assignments in one Markdown queue, dashboards in another tab, MCP keys and database tiers easy to mis-label in session reports.

Internal. You spend stand-up time restating which directory the agent is bound to instead of reviewing diff quality.

Philosophical. Operators deserve console ergonomics as honest as engineers expect from CI dashboards — without pretending a single SaaS SKU owns every repo.

Guide

DevPlane runs as its own checkout: start it against an absolute toolbox path (`npm start` from your devplane directory) and the dashboard scopes missions, CAPABILITIES lookups, MCP wiring, and the pattern library docs to that workspace. It does not import the toolbox runtime; integration is procedural — canonically described from the toolbox vantage in docs/DEVPLANE-INTEGRATION.md.

Abstract

Background. Consolidated repos still leave operators juggling clones, MCP keys, and PAT queue truth across surfaces; spreadsheets and ad-hoc Notion shards lose determinism autonomous agents rely on.

Methodology. DevPlane concentrates mission templates, reusable pattern catalogs, MCP server hooks, and dashboards around a consciously chosen working directory — the same binding pattern described in this repository's operator integration guide rather than speculative feature claims.

Scope. Operational console + documentation hub; algorithms and analytical contracts remain in product repos (People Analytics Toolbox, Performix, Meta-Factory, Principia).

Contribution. Gives fleets a single choke point for CAPABILITIES-aligned patterns (read the pattern in devplane, land code here) consistent with MULTI-REPO-WORKFLOW guidance referenced from AGENTS.md.

Evidence / Provenance. Ships outside this deploy — credibility rests on cloning people-analyst/devplane alongside this repo plus the live curl to its public marketing host below.

Plan

  1. 01

    Bind DevPlane to a working directory

    Start the operator dashboard scoped to people-analytics-toolbox exactly as documented in DevPlane onboarding — keep Cursor's workspace aligned with that path when agents run in parallel.

  2. 02

    Render missions plus assignment queue

    Translate PAT cards rendered from docs/ASSIGNMENT-QUEUE.md into dispatchable missions; treat DevPlane outputs as procedural truth, not runtime imports between products.

  3. 03

    Cross-link documentation

    Keep portfolio patterns (operator-console visuals, master patterns, toolbox aggregates) discoverable fleet-wide without drifting copies into orphaned wikis.

Call to Action

Direct. Visit devplane.dev — the public landing answers how to bind the dashboard to clones.

Transitional. Mirror this repo's canonical integration narrative anytime you compare database tiers versus DevPlane-hosted operator surfaces.

Spoke I/O (visual language v1)

Portfolio members reuse the toolbox’s Spoke I/O visual language — composition view vs. toolbox microservice boundaries documented in PAT-PROTOCOL-A §15. Source package: @people-analytics-toolbox/spoke-illustrations.

DevPlane — portfolio composition viewINPUTSMAIN ACTIONSOUTPUTSAssignment cards · missionsMarkdown + PAT idsGit workspace stateclone · branch · driftAgent run tracesCursor / MCP handoffsDispatchKanbanCross-repo doc hubDispatched missionsMission JSONAudit trail rowsoperator log · claimsPattern library refsCAPABILITIES paths↳ scoped to cwd↳ no runtime import across reposCOMPOSES WITHpeople-analytics-toolboxperformixprincipiameta-factoryfleet repos

Try it now

Copy this curl — it targets https://devplane.dev on its own deploy, not People Analytics Toolbox production URLs.

devplane.public-root

GET

Public marketing host responds 200 OK — runnable curl proof of the separately deployed surface (deep API routes remain defined in DevPlane docs, not here).

curl -sS "https://devplane.dev/"

Source repository · separate build

There is nothing to vendor from src/spokes/*/contracts inside this toolbox deploy — the portfolio member publishes its contracts from its home repository and ships on its own CI.

Try in Dev ConsoleOpen devplane.devSee the in-repo Principia bridge spokeBack to all spokes

Failure

Operators keep juggling tabs; MCP audit rows reference the wrong DATABASE_URL tier and reproducing PAT work across machines stays tribal knowledge.

Success

Missions dispatch with explicit cwd claims — documentation, MCP auth, and database assumptions stay anchored to the same deterministic story across the fleet.