Monk Loom

Architecture and authority boundary

Five deliberately separate responsibilities

LayerOwnsDoes not own
Federation Image v2Bytes, section geometry, integrity, capabilities, image identityPolicy decisions or learned meaning
MonkScoped rules, routing, search classification, validation and denialStatistical learning
Monk LoomBounded inference, evidence, adaptation proposalsExecution authority or commits
Perl specialist agentIntent classification, reviewed answers, and optional fixed workspace-action proposal dataReview, application, VFS commit, policy, build, or release authority
Chronicle, transaction, and hostUser authorization, validation, review, ordinary commands, atomic promotionUnreviewed autonomous learning

Binding

The attachment stores the SHA-256 fingerprint of the exact canonical Monk profile. Readers reject a mismatched or orphaned attachment. A policy edit therefore requires an explicit attachment review and rebind; old learned state is never silently carried onto semantically different policy.

Data flow

  1. The host derives named, bounded feature values.
  2. Loom validates the complete feature mapping and runs integer inference.
  3. The host receives advisory evidence with model and Monk fingerprints.
  4. If configured for adaptation, verified feedback binds to that evidence fingerprint.
  5. Loom returns a new attachment proposal. Nothing is committed.
  6. The host may review, validate, rebuild, verify, and promote through the normal VFS transaction path.

Agent proposal flow

  1. A validated, quality-accepted branch bundle is registered by fingerprint.
  2. A human accepts that exact bundle for submitting plans.
  3. An answer’s stored action recipe is bound to one workspace/configuration fingerprint.
  4. Chronicle dry-runs and displays every ordinary command.
  5. A named reviewer accepts or rejects the plan without applying it.
  6. A named operator separately reapplies validation and atomically saves the commands.
  7. Build and export remain independent, verified operations.

There is no call from Loom or a Perl agent into authorization, arbitrary file mutation, Monk-policy editing, image promotion, or release publication.