Pointer domains

The Pointer Engine maps repository paths to homes — declared places where a kind of artifact must live. pointer_enforce fails when governed content points at a missing path, when a file has no home, or when docs drift from the map.

What a pointer home is

A home is a stable directory (or file pattern) for a concern: routes, components, docs, assets, policies. Agents must create and update files inside the declared home instead of inventing parallel trees.

# Example pointer home map (conceptual)
site:        src/routes/
docs:        docs/
assets:      static/
components:  src/lib/components/
routes:      src/routes/

# pointer_enforce fails when docs claim a path that no longer exists,
# or when a governed file has no declared home.

Typical domains

• site / routes — application routes and pages
• docs — human documentation that must track real paths
• components — UI building blocks
• assets — static media
• ags-policy — .ags/*.yml governance configs

Agent usage

// MCP
pointer_enforce {}
// Returns path issues + suggested homes for orphaned files.

Works with

• Canonicalization — pointers say where things live; canonical says which file is the SoT.
• Semantic domains — pointer concepts belong to the pointer domain in the constraint graph.

Interactive drift visualization: Pointer showcase.