112 lines
3.4 KiB
Markdown
112 lines
3.4 KiB
Markdown
# Agent Invocation Packet: topic-discovery-router
|
|
|
|
## 1. Invocation Identity
|
|
|
|
- project_id: 2026-06-05-失望性情感隔离
|
|
- workflow: viewpoint-discussion-distillation
|
|
- stage: topic-discovery
|
|
- run_id: 2026-06-05-失望性情感隔离
|
|
- participant_id: topic-discovery-router
|
|
- target_participant_name: Topic Discovery Router
|
|
- participant_type: ccpe_agent
|
|
- canonical_artifact_path: `C:\Users\wangq\Documents\Codex\ccpe-system\agents\agent-specs\topic-discovery-router.agent.md`
|
|
- canonical_artifact_version: 0.1
|
|
- invocation_mode: blocked_pending_user_confirmation
|
|
- packet_type: orchestrator_index
|
|
|
|
## 2. Canonical Artifact Handling
|
|
|
|
- should_paste_full_prompt_or_spec: pending
|
|
- prompt_to_send_path: `invocations/topic-discovery-router/prompt-to-send.md`
|
|
- role_integrity_requirement: preserve topic-discovery-router role; do not act as builder or auditor
|
|
- allowed_wrapper_instructions: use Knowledge Vault invocation and context-management policies
|
|
- forbidden_role_changes: do not write topic docs; do not run final coverage audit; do not decide downstream execution
|
|
- no_simulation_requirement: yes
|
|
|
|
## 3. Current Task
|
|
|
|
Discover candidate topic graph from accepted source block inventory and sufficient source context, then return a topic-map draft with source block references, scope, anti-scope, confidence, merge/split proposals, low-confidence items, and downstream task candidates.
|
|
|
|
## 4. Input Files
|
|
|
|
```text
|
|
00-source-map.md
|
|
invocations/conversation-segmentation/source-block-inventory.csv
|
|
diary/2026/2026-06/2026-06-05.md
|
|
```
|
|
|
|
## 5. Context Files
|
|
|
|
```text
|
|
skills/invocation-policy.md
|
|
skills/context-management-policy.md
|
|
skills/knowledge-processing/viewpoint-discussion-distillation/context-strategy.md
|
|
C:\Users\wangq\Documents\Codex\ccpe-system\agents\agent-specs\topic-discovery-router.agent.md
|
|
```
|
|
|
|
## 6. Embedded Inputs
|
|
|
|
```text
|
|
source_document_path: diary/2026/2026-06/2026-06-05.md
|
|
source_map_path: 00-source-map.md
|
|
source_block_count: 40
|
|
round_count: 7
|
|
```
|
|
|
|
## 7. Output Contract
|
|
|
|
Returned output must follow:
|
|
|
|
```text
|
|
- Topic Summary
|
|
- Topic Scope And Anti-Scope
|
|
- Source Block Routing
|
|
- Downstream Task Candidates
|
|
- Merge / Split Proposals
|
|
- Low-Confidence Items
|
|
- Human Decisions Needed
|
|
```
|
|
|
|
The runtime may write `01-topic-map.md` only after a real participant output is returned and saved with source metadata.
|
|
|
|
## 8. Continuity Policy
|
|
|
|
Topic discovery should be run by a bounded participant strategy. If the full source is too long, use worker context packs by round or source block batch, then synthesize only from file-backed returned outputs.
|
|
|
|
## 9. Session Logging
|
|
|
|
Real returned output must be saved under:
|
|
|
|
```text
|
|
invocations/topic-discovery-router/returned-output.md
|
|
```
|
|
|
|
If external or manual execution is used, record platform, date, prompt path, and operator note.
|
|
|
|
## 10. Forbidden Actions
|
|
|
|
```text
|
|
- Do not simulate topic-discovery-router output in the main session.
|
|
- Do not finalize topic-map without user review.
|
|
- Do not route material into topic docs before topic-map confirmation.
|
|
- Do not treat source-map locator text as sufficient source content when topic classification needs more evidence.
|
|
```
|
|
|
|
## 11. Return Path
|
|
|
|
```text
|
|
invocations/topic-discovery-router/returned-output.md
|
|
01-topic-map.md
|
|
03-run-notes.md
|
|
```
|
|
|
|
## 12. Runtime Acceptance Rule
|
|
|
|
Current status:
|
|
|
|
```text
|
|
blocked_waiting_for_participant_output
|
|
```
|
|
|
|
The next step requires user confirmation of invocation mode and source context packaging.
|