Author’s extension

The agent stack must be described and versioned

This layer does not yet exist in Multica’s core. What follows is the principle behind my declarative extension: if a pipeline affects code, its changes must be comparable, reversible, and testable against data.

In my extension, agents, skills, tools, the MCP environment, permissions, and execution policy are described declaratively and versioned with Git. Configuration therefore gains a diff, history, and rollback path instead of remaining implicit state on a particular machine.

Coder.Unity v17

ui-layout@3 · basic screenshot check · model A · MCP tools set 1

Coder.Unity v18

ui-layout@4 · prefab identification rule · visual verification · MCP tools set 2

A version should answer three questions: what changed, which tasks it is recommended for, and on which runs—and with which metrics—it demonstrated an improvement. Then arguments about prompts and skills become engineering discussions instead of matters of taste.

Act II conclusion

Agentic execution becomes a system object

The local factory becomes a shared production system. The team gains common reference points: it can discuss a specific agent, a specific skill version, a specific execution trace, and a specific result cost.

describelaunchobserveupdatemeasurediscuss