164 lines
4.8 KiB
Markdown
164 lines
4.8 KiB
Markdown
# Writing Workbench Context Handoff
|
|
|
|
This document preserves the working agreements that led to this workspace. It exists so future Codex sessions do not depend on copied chat history.
|
|
|
|
## Confirmed Architecture
|
|
|
|
```text
|
|
Knowledge Vault = mine and archive
|
|
Writing Workbench = article production stage and process record
|
|
CCPE System = actor, skill, model, and runtime factory
|
|
Delivery Systems = deployable external agentic systems
|
|
Video Workbench = future dimensional video output workspace
|
|
```
|
|
|
|
The user described the metaphor this way:
|
|
|
|
```text
|
|
Knowledge Vault provides the script material.
|
|
Writing Workbench is the stage.
|
|
CCPE System provides actors, skills, model cards, and runtime protocols.
|
|
The user remains the final director, editor, and decision gate.
|
|
```
|
|
|
|
## Knowledge Vault Status
|
|
|
|
`C:\Users\wangq\Documents\Codex\knowledge-vault` has been established and migrated except for some work assets.
|
|
|
|
Important directories:
|
|
|
|
- `diary/`: daily or irregular captures from phone and PC
|
|
- `discussions/`: viewpoint base camp and historical process archive
|
|
- `sayings/`: formal essays
|
|
- `rules/`: human-facing model documents and writing rules
|
|
- `prompts/`: legacy and current prompt assets
|
|
- `sources/`: Deep Research, reading notes, excerpts, clipped articles, references
|
|
- `indexes/`: maintained mostly by Codex on request
|
|
- `templates/`: human-facing document templates
|
|
|
|
Writing Workbench should not recreate diary or generic discussion intake.
|
|
|
|
## Writing Workbench Role
|
|
|
|
This workspace begins only after the user decides to turn an idea into an article.
|
|
|
|
It should preserve the full production trail:
|
|
|
|
1. creation plan
|
|
2. positioning
|
|
3. outline generation and review
|
|
4. drafting
|
|
5. draft review
|
|
6. appendix generation
|
|
7. metadata generation
|
|
8. optional tribunal
|
|
9. human-facing model writing
|
|
10. publish package
|
|
|
|
The current scaffold intentionally leaves the first project empty. A real article project should be created under:
|
|
|
|
```text
|
|
projects/active/YYYY-MM-DD-aNNN-temp-slug/
|
|
```
|
|
|
|
## Process Record Principle
|
|
|
|
The user's prior workflow retained discussion transcripts because single-agent workflows often lost coherence without them. Agentic Engineering should reduce copy-paste burden, but it should not discard process records.
|
|
|
|
For each writer or reviewer interaction:
|
|
|
|
- `session.md` records the discussion process
|
|
- `report.md` records the final result
|
|
- orchestrator reads reports and synthesis, not every full transcript
|
|
|
|
## Session Mechanism
|
|
|
|
Use separate sessions or background threads when context isolation is useful.
|
|
|
|
Recommended pattern:
|
|
|
|
```text
|
|
Article Production Orchestrator
|
|
prepares context packs
|
|
dispatches writer/reviewer sessions
|
|
receives written outputs
|
|
synthesizes reports
|
|
asks user for decisions
|
|
```
|
|
|
|
Continuity should be file-based, not conversation-context-based.
|
|
|
|
## Runtime Roadmap For CCPE System
|
|
|
|
The next CCPE work should be done in:
|
|
|
|
```text
|
|
C:\Users\wangq\Documents\Codex\ccpe-system
|
|
```
|
|
|
|
Recommended build sequence:
|
|
|
|
1. Upgrade and verify key single-agent experts as CCPE-Lite.
|
|
2. Run Scenario Probe before upgrading any Lite into Agent Spec or Skill.
|
|
3. Preserve useful Lite artifacts instead of forcing every actor into Agent/Skill/Runtime.
|
|
4. Build `Article Production Orchestrator` as an Agent Spec.
|
|
5. Build `Outline Review Runtime` first, because outline review is the most expensive and failure-prone stage.
|
|
6. Add small reusable Skills only where real workflow demand exists:
|
|
- context-pack builder
|
|
- review dispatcher
|
|
- review synthesis
|
|
- repair request builder
|
|
- source-map builder
|
|
- metadata generator
|
|
7. Validate with a trial article project in Writing Workbench.
|
|
8. Only after the outline runtime stabilizes, expand to the full article production runtime.
|
|
9. Add Tribunal and Modeling Committee later as sub-runtimes with their own coordinators.
|
|
|
|
Important prior CCPE rule:
|
|
|
|
```text
|
|
Scenario-first layering:
|
|
decide Lite / Agent Spec / Skill / Runtime / Model Card based on actual use scenario, not on a desire to over-engineer.
|
|
```
|
|
|
|
## Controller Model
|
|
|
|
Before Tribunal and Modeling Committee are added, use one primary controller:
|
|
|
|
```text
|
|
Article Production Orchestrator
|
|
```
|
|
|
|
Later, use:
|
|
|
|
```text
|
|
Article Production Orchestrator = total project coordinator
|
|
Tribunal Presiding Agent = sub-controller for tribunal judgment
|
|
Modeling Committee Facilitator = sub-controller for human model document production
|
|
```
|
|
|
|
Sub-controllers are needed when target outputs, decision criteria, role sets, context isolation, risk boundary, or rhythm differ substantially.
|
|
|
|
## Future Video Workbench
|
|
|
|
A future sibling project should be created for dimensional output:
|
|
|
|
```text
|
|
C:\Users\wangq\Documents\Codex\video-workbench
|
|
```
|
|
|
|
It should handle:
|
|
|
|
- series architecture
|
|
- angle proposals
|
|
- video outline
|
|
- storyboard logic
|
|
- voiceover
|
|
- image prompts
|
|
- image/audio assets
|
|
- editing notes
|
|
- publishing copy
|
|
|
|
It should not be folded into Writing Workbench.
|
|
|