You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 18e03b3
Browse filesBrowse the repository at this point in the historyBrowse files
- [source] method="git" so ABB restores 4b09df8 before evaluation (blocking
merge issue: agent/ is gitignored by design and must not be vendored)
- rename 50-kiroku -> 51-kiroku to avoid the 50- prefix collision with DefuzeX-AI#288/DefuzeX-AI#289
- binding: working title derived from input text so the requested topic drives
the native writing task (was fixed 'Untitled Document')
- binding: honor incoming RunnableConfig callbacks/tags/metadata and ABB's
thread_id; native writer+checkpoint reused per thread instead of rebuilt per
invoke; drives writer.graph.invoke directly (DocumentWriter.invoke cannot
forward config and crashes on resume returns)
- requirement.md: human review stages are auto-approved/skipped (stated
explicitly); cross-input memory limited by upstream single-shot design
- verified: with agent/ absent, ABB restored the source via git and the Docker
local smoke passed 1/1 (judge: pass; step 3 now responsive to prior turns)
Copy file name to clipboardExpand all lines: resources/agents/51-kiroku/requirement.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,14 +36,14 @@ The binding returns a mapping containing draft, title, document_specification, a
36
36
## Known Limitations or Prohibited Behaviors
37
37
38
38
- The SDK boundary is text only. The current Case service accepts plain text; this profile must not be treated as supporting structured JSON inputs.
39
-
- The binding uses a fixed minimal document specification. It does not accept caller-supplied section names, paragraph counts, document type, title, results, or reference lists.
40
-
- Title suggestion is disabled. The returned title may remain the fixed default unless the native workflow changes it.
39
+
- The binding uses a fixed minimal document specification. It does not accept caller-supplied section names, paragraph counts, document type, results, or reference lists. The working title is derived from the input text (first line or sentence) so the requested topic drives the native writing task; it is not caller-configurable beyond that.
40
+
- Title suggestion is disabled. The returned title is the input-derived working title unless the native workflow changes it.
41
41
- Citation and reference generation are disabled in this deployment. The final draft should not be evaluated as if it includes generated citations or a references section.
42
-
-No human-review behavior is available or testable. Native interrupt points are resumed with an empty instruction only. Evaluation must not require interactive approval, manual editing, or multi-turn review feedback.
42
+
-Human review is auto-approved, not performed. The upstream graph contains manual-review interrupt stages; in this deployment they are effectively skipped — every pause is resumed with an empty instruction, which the source conditional edges interpret as "review complete, proceed". No human feedback is fabricated, but no human actually reviews topic sentences, drafts, or reflections. Evaluation must not require interactive approval, manual editing, or multi-turn review feedback.
43
43
- This deployment does not produce files. The upstream UI save path, pandoc export, project directory creation, and Markdown, HTML, or DOCX artifacts are not exercised by the binding. File persistence and document export are not available capabilities here.
44
-
- The binding does not forward incoming LangChain or LangGraph RunnableConfig extras through the native public invoke. Config propagation is limited by the native API; adapter wiring, callbacks, tags, metadata, or proxy routes are not behavioral evaluation goals.
44
+
- The binding forwards incoming RunnableConfig callbacks, tags, metadata, and thread identity to the graph, bypassing the native DocumentWriter.invoke wrapper which cannot carry them. Behavior depending on additional proxy routes or custom adapter wiring beyond that is not an evaluation goal.
45
45
- Web search is mandatory. There is no supported no-search mode. Tavily access and a valid TAVILY_API_KEY environment variable are required. If this secret is missing, the binding should fail clearly rather than silently skipping research.
46
46
- OpenAI-compatible model credentials are supplied by the deployment's model interception. The profile must not require manually configured native OpenAI API keys on the host, and secret values must never be requested or reproduced.
47
-
-Each input is one independent document session. There is no persistent memory across inputs; later inputs do not revise or continue earlier drafts unless the new input restates the needed context.
47
+
-Cross-input memory is limited by the upstream design. The binding reuses the native writer and checkpoint when the harness supplies a stable thread identity, but the upstream graph is single-shot: each new input starts a fresh document task on that thread, so later inputs do not revise or continue earlier drafts unless the new input restates the needed context.
48
48
- Long-running behavior is bounded by the deployment timeout. Extremely broad or multi-document requests may not complete and should be evaluated as unsupported rather than answered with invented partial results.
49
49
- The agent must not claim capabilities not present in this deployment, such as file upload handling, image generation, citation verification, direct service control, or arbitrary code execution as a user-facing feature.
0 commit comments