opencode-manifold 0.5.4 → 0.5.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +67 -10
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -81,19 +81,62 @@ The Lead Dev will:
|
|
|
81
81
|
|
|
82
82
|
---
|
|
83
83
|
|
|
84
|
+
## Architecture: The Circuit Board Model
|
|
85
|
+
|
|
86
|
+
Think of a plan as a circuit board design:
|
|
87
|
+
|
|
88
|
+
| Agent | Role | Question |
|
|
89
|
+
|-------|------|----------|
|
|
90
|
+
| **Manifold** | Board Designer | "What is this board's intended function?" |
|
|
91
|
+
| **Clerk** | Systems Integrator | "How does this board interface with existing system?" |
|
|
92
|
+
| **Todo** | Process Engineer | "What's the assembly sequence?" |
|
|
93
|
+
|
|
94
|
+
This ensures every plan is:
|
|
95
|
+
- Clearly understood (Manifold clarifies)
|
|
96
|
+
- Architecturally sound (Clerk validates fitment)
|
|
97
|
+
- Actionably decomposed (Todo sequences)
|
|
98
|
+
- Double-checked (Manifold + Clerk review)
|
|
99
|
+
|
|
100
|
+
---
|
|
101
|
+
|
|
84
102
|
## Architecture
|
|
85
103
|
|
|
104
|
+
### Planning Phase (Pre-Dispatch)
|
|
105
|
+
|
|
86
106
|
```
|
|
87
107
|
User → points to plan file (any format)
|
|
88
108
|
│
|
|
89
|
-
|
|
90
|
-
|
|
91
|
-
│
|
|
92
|
-
|
|
109
|
+
Manifold (Phase 0: Ingest Clarity)
|
|
110
|
+
│ Validates requirements are clear
|
|
111
|
+
│ Assesses if input is granular
|
|
112
|
+
↓
|
|
113
|
+
Clerk (Phase 1: Research) — ALWAYS runs first
|
|
114
|
+
│ Searches codebase, wiki, graph
|
|
115
|
+
│ Answers: "How does this fit?"
|
|
116
|
+
↓
|
|
117
|
+
Todo (Phase 2: Decomposition) — Only if not granular
|
|
118
|
+
│ Creates task list with context awareness
|
|
119
|
+
│ Applies purity tags
|
|
120
|
+
↓
|
|
121
|
+
Manifold (Phase 3: Design Review)
|
|
122
|
+
│ Validates task list satisfies plan intent
|
|
123
|
+
│ Kickback to Todo if needed
|
|
124
|
+
↓
|
|
125
|
+
Clerk (Phase 4: Interface Validation)
|
|
126
|
+
│ Validates fitment against codebase
|
|
127
|
+
│ Kickback to Todo if needed
|
|
128
|
+
↓
|
|
129
|
+
User Approval
|
|
130
|
+
↓
|
|
131
|
+
```
|
|
132
|
+
|
|
133
|
+
### Implementation Phase
|
|
134
|
+
|
|
135
|
+
```
|
|
93
136
|
Plugin State Machine (TypeScript, zero LLM cost)
|
|
94
137
|
│
|
|
95
|
-
├── Phase 1: Clerk research
|
|
96
|
-
│ ├── codebase-index search
|
|
138
|
+
├── Phase 1: Clerk research (per task)
|
|
139
|
+
│ ├── codebase-index search + wiki lookback + graph entries
|
|
97
140
|
│ ├── Composes scoped prompt
|
|
98
141
|
│ └── Creates task log file
|
|
99
142
|
│
|
|
@@ -101,12 +144,12 @@ Plugin State Machine (TypeScript, zero LLM cost)
|
|
|
101
144
|
│ ├── Spawn Senior Dev → implementation
|
|
102
145
|
│ ├── Spawn Junior Dev → review (first word: COMPLETE or QUESTIONS)
|
|
103
146
|
│ ├── Loop up to 3×, then escalate to Debug
|
|
104
|
-
│ └── Debug → one loop with Senior+Debug, then escalate to Clerk retry
|
|
147
|
+
│ └── Debug → one loop with Senior+Debug, then escalate to Clerk retry
|
|
105
148
|
│
|
|
106
149
|
├── Phase 3: Clerk logging
|
|
107
150
|
│ ├── Appends design decisions to task log
|
|
108
151
|
│ ├── Updates index.md, appends log.md, updates graph entries
|
|
109
|
-
│ └── Returns to
|
|
152
|
+
│ └── Returns to Manifold
|
|
110
153
|
│
|
|
111
154
|
└── Phase 4: Test (optional)
|
|
112
155
|
├── If test defined → run, check output
|
|
@@ -119,12 +162,26 @@ Plugin State Machine (TypeScript, zero LLM cost)
|
|
|
119
162
|
|
|
120
163
|
| Agent | Model | Role |
|
|
121
164
|
|-------|-------|------|
|
|
122
|
-
| `manifold` | good tool calling + planning |
|
|
123
|
-
| `clerk` | conceptualizing + large context |
|
|
165
|
+
| `manifold` | good tool calling + planning | Board Designer — orchestrates planning and dispatch |
|
|
166
|
+
| `clerk` | conceptualizing + large context | Systems Integrator — researches codebase, validates integration |
|
|
167
|
+
| `todo` | planning | Process Engineer — decomposes plans into task lists |
|
|
124
168
|
| `senior-dev` | coding | Implementation specialist |
|
|
125
169
|
| `junior-dev` | cheap/small coding | Review agent |
|
|
126
170
|
| `debug` | coding + troubleshooting | Fresh perspective after 3 failed loops |
|
|
127
171
|
|
|
172
|
+
### Agent Specialization
|
|
173
|
+
|
|
174
|
+
**Planning Phase:**
|
|
175
|
+
- **Manifold** handles clarity assessment, design review, and final validation
|
|
176
|
+
- **Clerk** researches codebase integration (always runs first, even for granular inputs)
|
|
177
|
+
- **Todo** decomposes with full architectural awareness
|
|
178
|
+
|
|
179
|
+
**Implementation Phase:**
|
|
180
|
+
- **Clerk** composes scoped prompts and maintains wiki
|
|
181
|
+
- **Senior Dev** implements
|
|
182
|
+
- **Junior Dev** reviews
|
|
183
|
+
- **Debug** breaks deadlocks after 3 failed loops
|
|
184
|
+
|
|
128
185
|
The sr/jr/debug loop enables cost-efficient workflows: a strong sr-dev paired with a cheaper junior for review, and a different model for debug (fresh perspective). The key is diversity between sr and debug, not raw power. Junior's role as reviewer means a smaller/cheaper model works well — the sr/jr loop catches most issues, and debug's different reasoning approach breaks deadlocks.
|
|
129
186
|
|
|
130
187
|
---
|