first commit

This commit is contained in:
wantsong 2026-06-02 15:41:38 +08:00
parent 0640418eb1
commit 756a0846a0
19 changed files with 595 additions and 0 deletions

129
WORKBENCH.md Normal file
View File

@ -0,0 +1,129 @@
# WORKBENCH.md
## 1. Workspace Identity
This project is the article production workspace.
It is a stage and process black box for deep writing. It records how an article moves from selected idea to final published text, while keeping the original knowledge archive and CCPE asset factory separate.
## 2. Operating Principle
Preserve process as a first-class artifact.
The user values not only final drafts but also the discussion, review, synthesis, repair, and decision trail that produced them. Do not collapse multi-round writing or review work into a single final file unless explicitly asked.
## 3. Project Lifecycle
Ideas normally begin outside this workspace:
```text
knowledge-vault/diary
knowledge-vault/discussions
knowledge-vault/sources
knowledge-vault/sayings
knowledge-vault/rules
```
A project enters Writing Workbench only after the user decides to write.
Each active article should use a stable project id:
```text
projects/active/YYYY-MM-DD-aNNN-temp-slug/
```
Do not rename the project folder every time the article title changes. Store title changes in `project.md` and final title metadata in `publish/final.md`.
## 4. Canonical Article Project Structure
Use `templates/article-project/PROJECT_STRUCTURE.md` as the expansion guide when creating a full project.
Top-level project files:
- `project.md`: stable project identity, temporary title, final title when known, phase, status
- `source-map.md`: source files from Knowledge Vault and other repositories
- `status.md`: current phase, open decisions, next actions
Main stages:
- `00-creation-plan/`
- `01-positioning/`
- `02-outline/`
- `03-drafting/`
- `04-draft-review/`
- `05-appendix/`
- `06-metadata/`
- `07-tribunal/`
- `08-model-writing/`
- `publish/`
## 5. Session And Thread Policy
Use files as shared state.
Separate Codex sessions or background threads may be used for writers and reviewers, but their long conversation history should not be copied wholesale back into the orchestrator session.
Preferred flow:
```text
orchestrator session
prepares context-pack
dispatches writer or reviewer session
receives session.md and report.md
reads only the necessary report/synthesis
asks the user for decision when needed
```
For each review role, preserve:
- `session.md`: discussion/process record
- `report.md`: final review result
The orchestrator should consume reports and synthesis files, not every full session transcript.
## 6. Context Pack Policy
Do not feed every source file by default.
Prepare task-specific context packs:
- `context-pack-lite.md`: article goal, current outline/draft, core claims
- `context-pack-standard.md`: lite pack plus selected material summaries and key source links
- `context-pack-deep.md`: standard pack plus long source excerpts, historical essays, or Deep Research
Use the smallest pack that lets the role do useful work.
## 7. CCPE Consumption
Writing Workbench consumes CCPE assets from:
```text
C:\Users\wangq\Documents\Codex\ccpe-system
```
Examples:
- main writer agents
- Zhang Liao red-team agent
- Cognitive Imaging
- Giant Cognition
- metadata agent
- context-pack builder skill
- review synthesis skill
- repair request builder skill
- Article Production Orchestrator
- Outline Review Runtime
Do not duplicate the full canonical CCPE asset inside this workspace. Add thin notes in `ccpe-consumption/` that point to the canonical source and explain how this workspace uses it.
## 8. Archive Policy
When an article is completed:
- keep full process records in `projects/completed/`
- archive final essay in `knowledge-vault/sayings`
- archive human model documents in `knowledge-vault/rules`
- promote AI-facing model cards or runtime assets through `ccpe-system` only when mature enough
When a project is abandoned, move it to `projects/abandoned/` and preserve the reason in `status.md`.

View File

@ -0,0 +1,27 @@
# CCPE Runtime Links
This file records how Writing Workbench consumes CCPE System assets.
Canonical CCPE workspace:
```text
C:\Users\wangq\Documents\Codex\ccpe-system
```
## Planned Assets
| Asset | Type | Status | Notes |
| --- | --- | --- | --- |
| Article Production Orchestrator | Agent Spec | planned | Total writing process coordinator |
| Outline Review Runtime | Runtime | planned | First runtime to build and validate |
| Context Pack Builder | Skill | planned | Builds role-specific context packs |
| Review Synthesis | Skill | planned | Synthesizes multiple review reports |
| Repair Request Builder | Skill | planned | Turns review synthesis into writer repair instructions |
| Cognitive Imaging | Lite / Model Card | existing in CCPE | Use as review actor where applicable |
| Giant Cognition | Lite / Model Card | existing in CCPE | Use as review actor where applicable |
| Zhang Liao | Lite / Agent | planned | Red-team and constructive Socratic reviewer |
## Policy
Do not copy canonical CCPE artifacts here. Record links, usage notes, and task-specific adapters only.

163
docs/context-handoff.md Normal file
View File

@ -0,0 +1,163 @@
# 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.

View File

@ -0,0 +1,13 @@
# Active Projects
No active article projects yet.
When adding a project, record:
- project id
- temporary title
- current phase
- lead writer / style
- source-map path
- next action

View File

@ -0,0 +1,14 @@
# CCPE Consumption Map
This index tracks which CCPE assets were used by Writing Workbench projects.
Record:
- project id
- stage
- CCPE asset
- canonical path
- output path
- issues found
- improvement requests for CCPE System

View File

@ -0,0 +1,12 @@
# Completed Projects
No completed article projects yet.
When completing a project, record:
- project id
- final title
- final essay archive path in Knowledge Vault
- model documents extracted, if any
- CCPE assets triggered, if any

View File

@ -0,0 +1,16 @@
# Extracted Models
This index tracks human-facing model documents produced from article projects.
Final human-facing models should be archived in:
```text
C:\Users\wangq\Documents\Codex\knowledge-vault\rules
```
AI-facing model cards should be promoted through:
```text
C:\Users\wangq\Documents\Codex\ccpe-system\model-cards
```

View File

@ -0,0 +1 @@

1
projects/active/.gitkeep Normal file
View File

@ -0,0 +1 @@

View File

@ -0,0 +1 @@

1
templates/.gitkeep Normal file
View File

@ -0,0 +1 @@

View File

@ -0,0 +1,82 @@
# Article Project Structure
Use this structure when expanding a new active article project.
```text
YYYY-MM-DD-aNNN-temp-slug/
project.md
source-map.md
status.md
00-creation-plan/
creative-brief.md
writer-selection.md
series-position.md
context-pack.md
sessions/
01-positioning/
premise.md
main-writer-sessions/
positioning-final.md
02-outline/
context-packs/
main-writer-sessions/
outlines/
outline-v1.md
outline-v2.md
outline-final.md
review-rounds/
round-01/
review-brief.md
cognitive-imaging/
session.md
report.md
zhang-liao/
session.md
report.md
giant-cognition/
session.md
report.md
synthesis.md
repair-request.md
appendix-outline.md
03-drafting/
context-packs/
sessions/
chapters/
full-draft.md
04-draft-review/
review-rounds/
revision-plan.md
full-revised.md
05-appendix/
sessions/
appendix-draft.md
appendix-final.md
06-metadata/
metadata-session.md
metadata-draft.md
image-prompt.md
image-url.md
metadata-final.md
07-tribunal/
README.md
08-model-writing/
extraction-brief.md
sessions/
model-draft.md
model-final.md
destination-map.md
publish/
final.md
```

24
templates/context-pack.md Normal file
View File

@ -0,0 +1,24 @@
# Context Pack
## Pack Type
- lite / standard / deep
## Task
## Role Receiving This Pack
## Current Artifact
## Article Goal
## Core Claims
## Required Sources
## Selected Evidence
## Constraints
## Output Request

View File

@ -0,0 +1,22 @@
# Human Model Document
## Model Name
## Source Article
## Model Definition
## Core Structure
## Mechanism
## Applicable Scenarios
## Non-Applicable Scenarios
## Version Relationship
## Derivative Models
## AI Model Card Potential

View File

@ -0,0 +1,18 @@
# Metadata Request
## Article Path
## Target Output
- title
- subtitle
- keywords
- description
- tags
- categories
- image prompt
## Classification Rules
## Notes

24
templates/project.md Normal file
View File

@ -0,0 +1,24 @@
# Project
## Identity
- Project ID:
- Temporary title:
- Final title:
- Status: active
- Current phase:
- Created:
- Last updated:
## Intent
## Target Article Type
## Lead Writer / Style
## Series Position
## Human Decision Gates
## Notes

17
templates/review-brief.md Normal file
View File

@ -0,0 +1,17 @@
# Review Brief
## Review Target
## Reviewer Role
## Context Pack
## Review Objectives
## Known Concerns
## Required Output
- `session.md` for process record
- `report.md` for final review result

View File

@ -0,0 +1,16 @@
# Review Report
## Verdict
## Strongest Parts
## Critical Issues
## Structural Risks
## Missing Context Or Evidence
## Repair Suggestions
## Questions For User

14
templates/source-map.md Normal file
View File

@ -0,0 +1,14 @@
# Source Map
## Knowledge Vault Sources
## CCPE Sources
## External Sources
## Selected Materials
## Source Policy
This project references source files unless explicitly instructed to copy selected excerpts into local context packs.