# Project Relationships

This file is the local project map for The Mindscape of Bro Tsong. It exists so future Codex sessions know what this repository owns, what it requests from neighboring repositories, and when to pause instead of improvising missing tools.

## Local Identity

`the-mindscape-of-bro-tsong` is the product and application repository for The Mindscape of Bro Tsong.

The current phase is:

```text
model_library_mvp
```

This repository owns:

- Product-specific model library data
- Model JSON files
- Human-readable model cards used by this product
- Source article and evidence indexes selected for this product
- Regression cases for product model stability
- Selector rules and examples for this product
- Application implementation when the project later adopts frameworks such as CrewAI, LangGraph, or a server runtime
- Project-specific requirements, handoffs, validation reports, and decision records

This repository does not own canonical expert-agent specifications, reusable automation Skill source, or upstream source archives.

## Neighboring Projects

| Project | Relationship To This Repository | This Repository Consumes | This Repository Produces |
| --- | --- | --- | --- |
| `knowledge-vault` | Upstream source archive and discussion memory | canonical articles, source discussions, prior model material, planning records | selected source references, feedback about missing source organization |
| `ccpe-system` | Supplier for expert-agent architecture, model governance, runtime specs, and integration registrations | Agent Specs, Runtime Specs, Model Card rules, Model Index rules, invocation protocols, evaluation rubrics, integration registration guidance | capability requests under `requirements/ccpe/`, product feedback from real use |
| `skills-vault` | Supplier for reusable automation Skill source | installed automation Skills from `.agents/skills`, Skill usage rules, validated scripts or CLIs | capability requests under `requirements/skills-vault/`, reusable automation demand discovered during model extraction |
| `.agents/skills` | Local runtime installation surface | installed runnable Skills | no source ownership; runtime use only |
| `writing-workbench` | Related downstream writing workspace | possible writing-oriented usage feedback | model usage or output requirements if writing workflows later depend on this system |
| `video-workbench` | Related downstream dimensional-output workspace | requirement directory pattern and possible output workflow needs | model usage or output requirements if video workflows later depend on this system |

## Boundary Rules

- Product data, application code, selector behavior, and product-specific validation belong in this repository.
- Canonical Agent Specs, Runtime Specs, Model Index governance, no-simulation protocols, and integration registrations belong in `ccpe-system`.
- Reusable automation Skill implementation source belongs in `skills-vault`.
- Installed runnable Skills are used from `C:\Users\wangq\.agents\skills`, not imported directly from `skills-vault`.
- Upstream article archives and long discussion records remain in `knowledge-vault`; this repository stores selected source records and evidence references needed by the product.
- CrewAI, LangGraph, server routes, persistence, queues, deployment scripts, and application monitoring belong in this repository when they implement this product. CCPE may design the agent contract; it should not become the application runtime.

## Request Channels

This repository has two supplier request channels.

### CCPE Requests

Use:

```text
requirements/ccpe/
```

Use this channel when the project needs:

- Expert-agent definition
- CCPE-Lite prompt card
- Agent Spec
- Committee Spec
- Runtime Spec
- Model Card or Model Index governance
- Invocation protocol
- Evaluation rubric
- Integration registration for a framework, Skill, CLI, API, or installed capability

Do not store canonical CCPE artifacts in this repository. Store the request here, then let `ccpe-system` own the supplied artifact.

### skills-vault Requests

Use:

```text
requirements/skills-vault/
```

Use this channel when the project needs:

- Deterministic automation tool
- Script-backed Skill
- Batch processor
- Format conversion helper
- Validation helper
- Source splitting or extraction utility
- Installable local automation Skill
- Reusable CLI wrapper

Do not store reusable automation Skill source in this repository. Store the request here, then let `skills-vault` own the implementation source if the need becomes stable and reusable.

## Model Extraction Work Mode

Model extraction is a duplex workflow:

```text
1. Build or request the workflow and supporting tools.
2. Use the available tools to process model content.
```

During extraction, if a missing reusable capability is discovered:

1. Classify the missing capability.
2. If it is agent/spec/runtime/governance work, create a request in `requirements/ccpe/`.
3. If it is reusable automation/tooling work, create a request in `requirements/skills-vault/`.
4. Pause the dependent extraction step unless the project owner explicitly says this repository should solve the need directly.
5. Resume model extraction only after the required tool, Skill, spec, or rule is available, or after the owner changes the scope.

This prevents the model extraction phase from silently turning into uncontrolled framework building or tool development.

## Framework Rule

Third-party agentic frameworks such as CrewAI or LangGraph are allowed only when they serve a concrete product implementation need.

Routing:

```text
Framework contract, agent role, authority, evaluation, and integration registration -> ccpe-system
Framework implementation, adapters, state, deployment, and product behavior -> this repository
Reusable deterministic helpers discovered while implementing -> skills-vault request first
```

Do not adopt a framework only because it is available. Record the product reason, expected benefit, and boundary decision before introducing it.
