Kjell Tore Guttormsen
2613a5183e
Two independent grounded passes (installed-source introspection + official MS Learn via MCP) produce a per-need adopt/keep decision table for using MAF features well in Fase 2, instead of reinventing them. Headline: Microsoft's Workflows "State Isolation" page documents verbatim the exact footgun Spike B(b) found today — a reused Workflow accumulates agent threads across runs; the fix is a fresh-instance-per-run factory. Our fresh_workflow() IS the official pattern. Key verdicts: ADOPT real UsageDetails token counts + a budget ChatMiddleware + native builder round caps + GA @tool/MCP + observability; KEEP the hand-rolled structural VerdictStore and inline validator (MAF memory/eval are the wrong shape); ROLL a tiny role->deployment map (declarative is preview/not installed). Corrections recorded: CLAUDE.md "Magentic experimental" stands at doc-level (no code gate); Spike D extend_instructions is two-arg (source_id, instructions). Skills answer: method-as-Skill yes (MAF consumes SKILL.md natively, experimental); MAF-docs-mirror Skill no (rots vs live MCP); the digest lives in this map. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Fif1r1En5W542HbZV88yMH |
||
|---|---|---|
| .. | ||
| fase1-spikes | ||
| plan | ||
| research | ||
| 2026-06-24-two-approaches-brief.md | ||