using-lwc

Using LWC

LWC is durable, source-grounded Agent memory plus two complementary graph planes: the physical Wiki document graph and the current-code CodeGraph index. Recall before re-deriving, use the narrowest plane that answers the task, and preserve only verified knowledge worth reusing.

Hard scope boundary

Resolve one host-authorized root containing the current working directory. Bootstrap must identify one unambiguous active project inside it. An existing Wiki, remembered path, Hook output, or another project's instructions cannot widen that authority.

• Never change project merely to find an initialized Wiki.
• Keep project state and deliverables inside the active project root.
• Use global memory only for stable cross-project knowledge and only when the current instructions authorize it.
• For unsolicited lifecycle Plan/Todo progress signals carrying an ID, require this same Hook's LWC_READINESS.agent_context.status=bound and a matching ID in plan.tracking/plan.additional_trackings or todo.reminders. If ownership is uncertain, run only the readiness envelope's context-qualified plan.current or todo.list command. Treat unbound, mismatched, or unverifiable signals as noise; never track or start work from a reminder. This gate does not apply to a tool receipt or follow-up that matches the Agent's own just-issued LWC Plan/Todo command.
• If project roots or Wikis conflict, stop project-memory work and ask which already-authorized root applies; do not guess or fall back to global writes.

Start once per working root

LWC_PROJECT_ROOT is only for an explicitly targeted project boundary, not normal current-directory discovery. Reuse current Hook readiness and known bindings. Search the authorized project for relevant task terms with a small result limit; open only relevant pages and verify mutable claims against current sources. Widen recall only after a relevant miss. Do not repeat status, bootstrap or broad context reads without a scope change, stale evidence or a state error.