Define folder-backed Resource Profile semantics for Decision Tree carriers

[schickling-assistant]

Problem

The wasm Resource Profile/resync v1 realizes only no-follow regular files and identifies changes by hashing whole-file transitions.

Decision Tree instead denotes resources/decisions/: an append-only directory of immutable decision records. Registering it now would either produce dead configuration or falsely imply directory support. Q15 therefore selected the three regular-file self profiles for v1 and deferred Decision Tree (answer record mhlwew).

Contract to define

Before registering Decision Tree, define and prototype the observable folder-backed carrier contract:

• directory snapshots versus per-entry events
• occurrence identity and ordering
• create, rename, and remove semantics
• event coalescing
• no-follow traversal plus size and entry-count bounds
• recovery and transaction semantics
• self-subject and cross-seat containment

This issue is for settling and prototyping the contract, not prescribing an implementation prematurely.

References

• feat(resync): wasm-only Resource Profile foundation #351
• schickling/dotfiles#2055
• Decision Tree decision handle Q15, answer record mhlwew

Posted on behalf of @schickling

field	value
agent_identity	unknown
agent_persona	unknown
agent_supervisor	unavailable
agent_tool	unknown
agent_tool_version	unknown
agent_runtime	unknown
tooling_profile	dotfiles@e4789b0