5.0 KiB
CCPE Artifact Taxonomy
1. Purpose
This document defines the expanded artifact taxonomy for CCPE System.
Classification must precede creation, audit, refactor, migration, registration, or deletion.
2. Primary CCPE-Owned Artifact Types
2.1 CCPE-Lite
Portable expert prompt or Prompt Card.
Use when:
single expert role
human-facing interaction
Web / GPT / Gemini / Claude use
no heavy state or handoff requirement
portable prompt is the production artifact
Mature expert prompts should stay Lite by default unless real usage requires another layer.
2.2 CCPE-Agent
Durable role spec for a reusable working agent.
Use when:
stable responsibility
explicit input / output contract
collaboration or handoff
authority boundaries
evaluation requirements
possible tool or skill calls
2.3 CCPE-Committee
A fixed multi-agent review or judgment structure.
Use when:
multiple roles create necessary tension
independent reports are required
synthesis must preserve disagreement
human gate decides how to use the reports
no-simulation evidence is required
Committee is not a casual list of agents. It must define members, role tension, invocation rules, report schema, synthesis rule, and human decision gate.
2.4 CCPE-Skill
Reusable capability spec.
CCPE-Skill may be:
cognitive
method
workflow
evaluation
transformation
knowledge-management
CCPE-Skill is not the same as an installable automation script. A CCPE-Skill may be a method, checklist, reasoning protocol, or evaluation contract.
2.5 CCPE-Runtime
Protocol for multi-stage or stateful work.
Use only when the work involves:
multiple stages
multiple participants
state
handoff
tools
files
human gates
recovery
synthesis
archival
downstream dependency
Runtime does not imply full automation. Interactive Runtime is first-class.
2.6 Model Card
Reusable cognitive model definition.
Use when the artifact defines how to understand or reason about a class of problems, with assumptions, mechanism, scope, failure modes, and falsification boundary.
2.7 Model Index
Registry and map of Model Cards.
Use when models need taxonomy, dependency tracking, overlap tracking, usage mapping, or lifecycle governance.
2.8 Integration Registration
Architecture registration for a capability CCPE depends on but does not own.
Use for:
skills-vault automation skill
MCP server
CLI tool
API service
installed local capability
agentic development framework
Registration records dependency metadata, authority, safety, validation, failure behavior, and consumers.
3. Non-CCPE Ownership Categories
3.1 Project Runbook
Belongs in the project repository.
Examples:
writing-workbench project playbook
video-workbench production runbook
knowledge-vault discussion processing instructions
work-projects application workflow docs
CCPE may provide a Runtime spec or Agent spec that a runbook uses. The runbook itself belongs to the project.
3.2 Project Execution Record
Belongs in the project repository.
Examples:
session.md
returned reviewer report for one article
decision record
source digest for one project
draft chapter
editing checklist for one deliverable
3.3 automation Skill Source
Belongs in skills-vault.
Examples:
script-backed markdown cleanup
batch export
TTS batch generation
file renaming
source splitting
format conversion
CCPE may register such a skill when used by a CCPE Runtime or Agent.
3.4 Production Application Implementation
Belongs in the concrete development project.
Examples:
LangGraph node implementation
CrewAI agent class
server route
database state schema
queue worker
monitoring configuration
deployment scripts
CCPE may design the agent contract. It does not own the deployable implementation.
3.5 Out of Scope
If an artifact is not reusable architecture, not a project requirement, not an external capability registration, and not a cognitive model asset, it may be out of scope for CCPE.
4. Decision Matrix
| Input | Target |
|---|---|
| Mature Web expert prompt | CCPE-Lite |
| Expert prompt with stable embedded model | CCPE-Lite + optional Model Card |
| Durable workflow role | CCPE-Agent |
| Fixed multi-agent review structure | CCPE-Committee |
| Reusable cognitive method | CCPE-Skill |
| Deterministic script-backed tool | skills-vault automation Skill source |
| Multi-stage stateful process | CCPE-Runtime |
| One project runbook | project repository |
| One project output or decision log | project repository |
| External tool dependency | Integration Registration |
| Production app implementation | development project repository |
5. Minimality Rule
Select the smallest structure that preserves:
purpose fit
intellectual flavor
reuse value
boundary precision
authority clarity
evaluation strength
runtime safety
maintainability
Do not upgrade an artifact into Agent, Skill, Runtime, Committee, or Model Index layers merely because it is important.