Open questions
Questions the specification has not settled yet, and what each needs to be settled. A settled one stays in the table, struck through, with its answer.
| Id | Question | Needs |
|---|---|---|
| — | ||
| Q-2 | The license (MIT, Apache-2.0, or both). | the owner |
| Q-3 | Configuration format and location (TOML in the project and in the user's config directory?). | design |
| Q-4 | Do the chosen providers accept direct requests from a browser (CORS), and with which headers? | a check per provider |
| Q-5 | Which ratatui backend renders to the DOM well enough for the demo? | a spike |
| Q-6 | Out-of-process plugins in any language: when, and for which interfaces? | after M2 |
| Q-7 | A sandbox for third-party plugins (WebAssembly components)? | after M4 |
| Q-8 | Is "no harness runs in the browser" true? Check before saying it publicly. | research |
| Q-9 | Trigger configuration: the match syntax (label globs, payload field conditions), how a payload maps onto a journal entry or a skill's input (templates?), and per-trigger rate limits. | design |
| Q-10 | How a skill run started by a callback reports back to the caller: the callback's result URL, a reply callback, or a message to the user's channel? | design |
correlation_id or any id its product logic guarantees) sent with every flowstate_update; several instances render collapsed by default, the user opens any, a collapsed instance pulses for one second on an update (ADR 0012). | — | |
| Q-12 | How events of an existing process map onto a chart's nodes without changing the process: a mapping table in the binding, labels, payload fields? | design |
| Q-13 | Run history: retention, size limits, and which windows watch a chart (a named session, every session of the project, the one that created it). | design |
approve, step back only where possible, product routes; env-gated and authorized (CON-25, CON-27). The harness's own router is its daemon, the single callback entry point. | — | |
MULTITOOL_DEBUG_MODE=1, with authorization (CON-25). | — | |
approve, no timeouts, nothing on its own even if the agent is gone; a health check was rejected as over-engineering (CON-29). | — | |
Condition (IF-15, any logic, always a bool) turns true (ADR 0014). | — | |
| — | ||
| — | ||
| — | ||
true resend? | — | |
| — | ||
| — | ||
exec on Unix; a child in the same console on Windows), handing the in-memory view over through a hand-off file (ADR 0015). | — | |
| — | ||
| — | ||
PostToolUse hook on every write to the journal, a map or a chart tells it which file to update (ADR 0017). | — | |
Stop, the same checker as multitool docs check and in CI; structure only, not prose (CON-45, ADR 0017). | — | |
docs/ and .harness/ the harness asks once whether to initialize it (project-init creates both); no mirroring until then (ADR 0017). | — | |
.harness/ are committed..gitignore lines; revisited if something comes up in use (ADR 0017). | — | |
message removed (it is notification), journal only writes to the journal, skill kept as a concept (may be dropped), flow renamed flowstate_update (ADR 0009). | — | |
| Q-32 | Generated documentation (ADR 0018): the PDF engine — printed from the HTML, or a typesetting engine. (Settled by the owner: only the docs files are the source, not the journal; built on demand by multitool doc; CI is the project's DevOps choice.) | the owner |
| — | ||
| Q-34 | The delegate's default mode: oneshot or session, by time to first event and reliability. | a measurement |
| Q-35 | The delegate in long sessions: who compacts and whether the log stays in step, memory when idle, a dropped pipe, limits. | a two-hour run |