SoloCrew

Product Identity

SoloCrew is a local, founder-facing Engagement Operating product surface for one-person-company operations. It sits downstream of the Coregentis authority stack and turns bounded product/app evidence into reviewable local surfaces for a founder or operator.

Authority order:

MPLP Protocol -> Cognitive_OS -> SoloCrew

SoloCrew currently provides bounded local engagement evidence and review capabilities. It is a product repository and app/projection baseline, not the MPLP protocol source of truth and not the neutral Cognitive_OS runtime foundation.

What SoloCrew Does Today

Current SoloCrew product truth is best described with stable Engagement language rather than release-line object names.

Today the repo contains local, deterministic, review-oriented support for:

• A V3.0 deliverable Engagement Operating Loop stable line that composes local create/load engagement workspace records, a review-only local loop runner, a founder review packet object, a local session history ledger, and a deterministic in-memory export package object.
• Engagement lifecycle framing across candidate, onboarding, paid-pilot, post-pilot review, conversion review, and archival stages.
• A local founder review loop over app, shell, and projection-safe evidence.
• Engagement onboarding packet semantics for expectations, required inputs, support boundaries, source references, and no-claim posture.
• Engagement readiness view semantics for founder review of onboarding, feedback, support burden, and local evidence signals.
• Engagement evidence record semantics for feedback usefulness, continuation signals, permission posture, and support review context.
• Engagement review gate semantics for private reference review, anonymized quote review, legal review, hold decisions, deny-public-use decisions, and manual conversion review preparation.
• Active app/page/shell/projection surfaces migrating toward canonical Engagement aliases while retaining compatibility exports for historical V1.x/V2.x code.
• V2.5 semantic stabilization work that introduces canonical Engagement aliases, metadata contracts, and active-surface import migration without broad file renames or behavior changes.

These capabilities are local-only, manual-first, review-only, deterministic, and non-executing. They do not create external execution, public publication, automatic conversion, payment execution, package publication, or upstream protocol/runtime authority.

Current Stable Release

Current stable release:

• title: SoloCrew V3.0 Stable - Deliverable Engagement Operating Loop
• tag: solocrew-v3.0-stable-deliverable-engagement-loop-20260430
• target: 0bf949959ac1275d33e7983d64feed5ed5098b9e
• package_publish: false
• assets: empty

V3.0 Stable is a stable repository line for the Deliverable Engagement Operating Loop with limited local scope only. It validates local create/load engagement, workspace/session/loop/history composition, a review-only loop runner, founder review packet output, local session history ledger, and deterministic in-memory export package object.

V3.0 Stable remains local-only, manual-first, review-only, deterministic, non-executing, and in-memory. It does not create filesystem writes, database storage, persistence adapters, file export paths, cloud sync, SaaS sharing, public publishing, email/CRM automation, external analytics, LLM/model/agent/ tool invocation, customer account provisioning, automatic conversion, provider/channel dispatch, marketplace behavior, autonomous execution, package publication, or package assets.

V3.0 Stable remains below public/private beta, paid product readiness, commercial readiness, production readiness, MPLP certification, and MPLP endorsement.

V2.5 Stable remains preserved as the Product Semantic Stabilization / Engagement Canonicalization baseline:

• tag: solocrew-v2.5-stable-semantic-stabilization-20260429
• target: 4061f0df0cf6e5f151563c11ac94e27dabbd23b8

Current OPC True MVP Candidate Status

SoloCrew OPC True MVP Candidate: Ready with Constraints.

This status is true MVP candidate only. It is bounded, deterministic, local/test-only, projection-safe, non-executing, and intended for founder/operator dogfooding over the OPC Foundation loop, bounded browser route descriptors, and Dev/Media minimal work packet preparation.

It is not true MVP, not commercial MVP, and not a production release. It keeps no provider/model/worker bridge, no Dev Pack code/file/test action, no Media Pack publishing/final-content/message action, no external delivery, and no external or browser/database/network storage.

Evidence:

• internal candidate seal: governance/seals/SOLOCREW-OPC-INTERNAL-MVP-CANDIDATE-SEAL-v0.1.md
• true MVP candidate seal: governance/seals/SOLOCREW-OPC-TRUE-MVP-CANDIDATE-SEAL-v0.1.md
• readiness audit: governance/audits/SOLOCREW-OPC-INTERNAL-MVP-CANDIDATE-READINESS-AUDIT-v0.1.md
• true MVP gap audit: governance/audits/SOLOCREW-OPC-TRUE-MVP-GAP-AUDIT-v0.1.md
• route/form readiness audit: governance/audits/SOLOCREW-OPC-TRUE-MVP-BROWSER-ROUTE-AND-FORM-HANDLER-READINESS-AUDIT-v0.1.md
• bounded route/form implementation: governance/audits/SOLOCREW-OPC-TRUE-MVP-BOUNDED-ROUTE-AND-FORM-HANDLER-IMPLEMENTATION-v0.1.md
• route/form Dogfooding Run 07: governance/audits/SOLOCREW-OPC-TRUE-MVP-ROUTE-FORM-DOGFOODING-RUN-07-v0.1.md
• true MVP candidate readiness audit: governance/audits/SOLOCREW-OPC-TRUE-MVP-CANDIDATE-READINESS-AUDIT-v0.1.md

The true MVP gap audit is audit/planning only. It starts from the sealed internal candidate baseline, defines the preparation-only true MVP target and gap matrix, and keeps no browser route handlers, no form handlers, no provider/model/worker execution, no Dev Pack code/file/test action, no Media Pack publishing/final-content/message action, no external delivery, no external persistence, and no browser/database/network storage.

The route/form readiness audit is also audit/planning only. It authorizes only a later bounded implementation wave for visible route/page composition, safe summary-only form state, manual review local controls, Dev/Media packet preview, continuity/resume inspection, and forbidden-control renderer enforcement; it does not add provider/model/worker execution, storage, external delivery, or true/commercial MVP status.

The bounded route/form implementation now defines deterministic visible route structures, safe summary-only local goal form state, local/manual review controls, Dev/Media packet previews, continuity/resume inspection, and forbidden-control boundary assertions. This remains local/test-only, preparation-only, non-executing, storage-free, and below true/commercial MVP status.

Run 07 dogfoods those route/form structures as a local/manual inspection run. It records preparation-workbench value for goal capture, packet preview, manual review, and continuity/resume, then selects true MVP candidate readiness audit as the next bounded task. It remains below true/commercial MVP status and adds no browser route handlers, form handlers, provider/model/worker execution, external delivery, or storage.

The true MVP candidate seal records SOLOCREW_OPC_TRUE_MVP_CANDIDATE_READY_WITH_CONSTRAINTS, keeps the preparation-only boundary frozen, and authorizes only SOLOCREW-OPC-COMMERCIAL-MVP-GAP-AUDIT. This remains a preparation-only, local/test-only, non-executing candidate status; it is not commercial-ready, not production-ready, and it adds no provider/model/worker execution, external delivery, or storage.

Personal Local Workbench

SoloCrew now includes a Jearon personal local dogfooding workbench. It is a practical local-use loop for turning a bounded real goal into copyable, savable, and resumable Dev and/or Media preparation artifacts.

Roadmap position:

OPC True MVP Candidate
-> Personal Local MVP V0 / Founder Dogfood MVP
-> Personal Dogfooding Run
-> Personal MVP Seal
-> Commercial Preparation Pilot
-> Commercial MVP
-> Multi-Cell AI Native Company OS

This is part of the SoloCrew path toward company OS, not a separate product branch. It validates the first real founder/operator loop before returning to commercial pilot dogfooding.

Run a direct local session:

npm run local:workbench -- --goal "Prepare next SoloCrew dev wave and LinkedIn post" --path both

Run the committed sample:

npm run local:workbench:sample

Generated sessions are written under:

.solocrew/local-workbench/sessions/<session-id>/

Each session can generate:

• session.json
• dev-packet.md with task-id candidate, objective, baseline, likely files, acceptance criteria, verification checklist, final-report requirements, and a copyable Codex prompt candidate
• media-brand-packet.md with separate LinkedIn and X preparation briefs, proof chain, do-not-say lists, tone boundary, public-safety boundary, and manual review checklist
• review.md
• resume.md with review state, output-value rating, packet readiness, and recommended next wave
• boundary.md
• index.md with files to open first, output value summary, and packet readiness

The global local index is written to:

• .solocrew/local-workbench/index.json
• .solocrew/local-workbench/index.md

The global index records each session's review state, output-value rating, recommended next wave, packet readiness, and latest resume path.

Recommended daily usage:

1. Start with one bounded development or media/brand goal.
2. Run npm run local:workbench with --path dev, --path media_brand, or --path both.
3. Open index.md or resume.md in the generated session folder.
4. Copy the relevant preparation packet into Codex, ChatGPT, or a manual drafting workspace only after reviewing it.
5. The next day, reopen .solocrew/local-workbench/index.md and continue from the latest resume file.
6. Use the Dev packet's Codex prompt candidate or the Media packet's LinkedIn/X preparation brief as preparation material only, then manually review and edit before any next action.

This workbench is Jearon personal local dogfooding usable. It is not commercial-ready, not customer-ready, and not production-ready. It does not call models, execute code, modify project source files as a Dev Pack action, run tests as a Dev Pack action, publish content, generate final public content, send messages, deliver externally, or create browser/database/network storage. It creates local Markdown/JSON preparation artifacts only, and generated session files are ignored by git.

Governance evidence:

• personal local workbench implementation: governance/audits/SOLOCREW-PERSONAL-LOCAL-WORKBENCH-V0-IMPLEMENTATION-v0.1.md
• personal local MVP route-position record: governance/audits/SOLOCREW-PERSONAL-LOCAL-MVP-V0-IMPLEMENTATION-v0.1.md
• Personal Local MVP Dogfooding Run 01: governance/audits/SOLOCREW-PERSONAL-LOCAL-MVP-DOGFOODING-RUN-01-v0.1.md
• Personal Local MVP output value hardening: governance/audits/SOLOCREW-PERSONAL-LOCAL-MVP-OUTPUT-VALUE-HARDENING-v0.1.md

Read-only Personal Console

The runtime-backed Personal Console can be generated as a local read-only HTML page for inspection:

npm run personal:console:preview

The preview command writes:

.solocrew/personal-console/index.html

Open that file in a browser to inspect the /personal-console route page. The page renders the twelve Personal Console sections from the runtime-backed render model and shows Cognitive_OS Personal MVP runtime availability through the public projection bundle.

The page is intentionally read-only. Provider/model/tool/worker execution, publishing, payment, outreach, external action, automatic mutation, autonomous acceptance, training, and writeback are blocked.

V3.0 Stable Scope

V3.0 Stable release is verified for the First Deliverable Engagement Operating Loop. The stable line is limited local scope only:

• local-only
• manual-first
• review-only
• deterministic
• non-executing
• in-memory export object only

V3.0 Stable covers local engagement create/load, workspace/session/loop/history contracts, the review-only loop runner, founder review packet output, local session history ledger, and deterministic in-memory export package object.

V3.0 Stable does not publish packages, create package assets, change route URLs, create filesystem writes, create database storage, introduce a persistence adapter, create a file export path, add cloud sync or SaaS sharing, publish public material, send email, automate CRM, add external analytics, invoke LLM/model/agent/tool calls, provision customer accounts, automate conversion, dispatch to providers/channels, create marketplace behavior, or add autonomous execution.

V3.0 Stable does not modify Cognitive_OS or MPLP-Protocol. It does not claim public beta, private beta, paid product readiness, commercial readiness, production readiness, MPLP certification, or MPLP endorsement.

Semantic Stabilization Line

V2.5 is the Product Semantic Stabilization / Engagement Canonicalization line. It is not a cosmetic detour and it is not a shortcut into V3.0. This line keeps current product semantics in stable Engagement language while preserving release evidence.

Completed V2.5 stabilization work:

• canonical Engagement metadata contract: app/engagement/engagement-metadata-contract.ts
• canonical Engagement alias contract: app/engagement/engagement-canonical-contract.ts
• active compatibility alias layer: app/engagement/engagement-compatibility-aliases.ts
• active app/page/shell/projection import migration toward compatibility aliases, covered by tests/app/engagement-active-surface-import-migration.test.ts
• RC readiness gate passed with remaining compatibility debt, making V2.5 eligible for the bounded RC prep and conditional prerelease gate only.
• RC prerelease executed as semantic stabilization evidence: solocrew-v2.5-rc-semantic-stabilization-20260429 -> f98b29a9ab20bb02e9928f844d4fb1f761ba2031.
• Post-RC verification passed with remaining compatibility debt, making V2.5 eligible for the bounded stable prep and conditional release gate only.

Remaining active version-bearing runtime/product semantics are expected compatibility debt for this line. They are preserved as compatibility aliases, release evidence, fixture/regression evidence, or active product debt for a later authorized cleanup, not treated as a reason to rename historical files or remove versioned exports during RC prep.

Version numbers remain valid in release evidence, changelog entries, governance records, migration records, compatibility adapters, and historical fixtures/tests. They should not be the canonical shape of new domain objects, workflow helper names, field names, source-ref names, route constants, or current product capability names.

Architecture / Authority Boundary

SoloCrew is the downstream product/app repository.

Cognitive_OS is the upstream runtime foundation inspected by this repo. This repo consumes projection-safe runtime posture and bounded summaries where authorized, but it does not redefine Cognitive_OS law or mutate Cognitive_OS.

MPLP-Protocol is the protocol authority above Cognitive_OS and SoloCrew. This repo does not redefine MPLP law, does not publish MPLP artifacts, and does not claim MPLP certification or MPLP endorsement.

Current SoloCrew surfaces preserve local product boundaries:

• local-only
• manual-first
• review-only
• non-executing
• deterministic
• product-local unless a separately authorized upstream wave says otherwise

What This Is Not

SoloCrew currently is not:

• public beta
• private beta
• paid product ready
• commercial ready
• production-ready
• SaaS
• package published
• MPLP certification
• MPLP endorsement

SoloCrew currently does not implement:

• payment processor
• checkout
• subscription
• automated billing
• CRM or email automation
• public publishing
• testimonial or public case-study publishing
• external analytics
• LLM/model/agent/tool invocation
• provider/channel dispatch
• marketplace
• customer account provisioning
• automatic conversion
• autonomous execution

Release History and Evidence

Release history is preserved in tags, release records, audit records, planning records, and CHANGELOG.md. The list below is a concise product-entry index, not a replacement for immutable governance evidence.

Recent release evidence:

Line	Identity	Evidence
V3.0 Stable	solocrew-v3.0-stable-deliverable-engagement-loop-20260430 -> 0bf949959ac1275d33e7983d64feed5ed5098b9e	governance/releases/SOLOCREW-V3.0-POST-STABLE-VERIFICATION-MAINTENANCE-GATE-v0.1.md
V3.0 RC	solocrew-v3.0-rc-deliverable-engagement-loop-20260430 -> 11bc8666553f32548eb2dd997fdac1316bbdd490	governance/releases/SOLOCREW-V3.0-RC-POST-RELEASE-VERIFICATION-AND-STABLE-READINESS-GATE-v0.1.md
V2.5 post-stable maintenance gate	solocrew-v2.5-stable-semantic-stabilization-20260429 -> 4061f0df0cf6e5f151563c11ac94e27dabbd23b8	governance/releases/SOLOCREW-V2.5-POST-STABLE-VERIFICATION-MAINTENANCE-GATE-v0.1.md
V2.5 Stable	solocrew-v2.5-stable-semantic-stabilization-20260429 -> 4061f0df0cf6e5f151563c11ac94e27dabbd23b8	governance/releases/SOLOCREW-V2.5-STABLE-PREP-SEAL-AND-CONDITIONAL-RELEASE-RECORD-v0.1.md
V2.5 RC	solocrew-v2.5-rc-semantic-stabilization-20260429 -> f98b29a9ab20bb02e9928f844d4fb1f761ba2031	governance/releases/SOLOCREW-V2.5-RC-PREP-SEAL-AND-CONDITIONAL-RELEASE-RECORD-v0.1.md
V2.5 semantic stabilization	canonical Engagement aliases and active-surface migration	governance/planning/SOLOCREW-SEMANTIC-NAMING-CORRECTION-AND-DELIVERY-LINE-GOVERNANCE-v0.1.md; CHANGELOG.md
V2.4 Stable	solocrew-v2.4-stable-commercialization-readiness-loop-20260428 -> 12d7ccb00506670992b798d82aa81fbc0f5578f6	governance/releases/SOLOCREW-V2.4-POST-STABLE-VERIFICATION-MAINTENANCE-GATE-v0.1.md
V2.4 RC	solocrew-v2.4-rc-commercialization-readiness-loop-20260428 -> ea882d590b1b59c5b9ce703869fdd7abe66ff77d	governance/releases/SOLOCREW-V2.4-RC-POST-RELEASE-VERIFICATION-AND-STABLE-READINESS-GATE-v0.1.md
V2.3 Stable	solocrew-v2.3-stable-first-paid-pilot-loop-20260428 -> c111e2dd7811ec77903a1a139c33bb1a7bc0c27a	governance/releases/SOLOCREW-V2.3-POST-STABLE-VERIFICATION-MAINTENANCE-AND-V2.4-OPENING-GATE-v0.1.md
V2.3 RC	solocrew-v2.3-rc-first-paid-pilot-loop-20260428 -> 2dbdba7b8b3824d0e332c5237ab307ae1fe1ba65	governance/releases/SOLOCREW-V2.3-RC-POST-RELEASE-VERIFICATION-AND-STABLE-READINESS-GATE-v0.1.md
V2.2 Stable	solocrew-v2.2-stable-private-alpha-journey-20260428 -> aaef0147290848c35e68d8eb4e84616f904454e3	governance/releases/SOLOCREW-V2.2-STABLE-POST-RELEASE-VERIFICATION-AND-V2.3-ENTRY-GATE-v0.1.md
V2.2 RC	solocrew-v2.2-rc-private-alpha-journey-20260428 -> cb9ee1420181318d7198bd0bddc4896c6d3fe1d7	governance/releases/SOLOCREW-V2.2-RC-POST-RELEASE-VERIFICATION-AND-STABLE-READINESS-GATE-v0.1.md

Earlier V1.x, V2.0, and V2.1 evidence remains available through CHANGELOG.md, governance/releases/, governance/release/, governance/baselines/, governance/planning/, and governance/audits/. Those historical records should be preserved as release trace, not copied into new canonical product object names.

Development / Test Status

The latest full repository suite run for the V3.0 post-stable verification line reported:

• npm test -> pass, 716/716
• V3.0 deliverable engagement loop E2E tests -> pass
• V3.0 IMPL-01..05 focused tests -> pass
• canonical Engagement alias and metadata tests -> pass
• active-surface import migration test -> pass

This repository remains private package metadata only. No package publish is part of the current line.

Next Line

The next allowed work after V3.0 post-stable verification is V3.0 maintenance only.

Allowed maintenance examples include release artifact correction, documentation alignment, test/gate correction, no-claim hardening, compatibility alias repair, deterministic fixture/test repair, typo/link correction, evidence backfill, non-behavioral governance cleanup, or a limited local loop bugfix that does not add new capability.

No V3.1 planning is opened automatically. Any future V3.1 planning or commercial-readiness planning requires explicit owner authorization first. Maintenance must not create package publish, package asset, public/private beta claim, paid/commercial/production readiness claim, Cognitive_OS change, MPLP-Protocol change, MPLP certification, MPLP endorsement, or new product capability. No additional V3.0 implementation scope is opened by this README structure.