rawr-hq-template

Mental model for a sealed service whose context and authorship narrow toward operation handlers.

Mental model for locating work in RAWR's blueprint kinds while keeping semantic direction, ownership, and structural proof distinct.

Mental model for Nx as the repository graph and scheduler while project owners retain their qualified build and verification work.

Mental model for one conventional installed Oclif application that owns CLI identity while commands retain qualified capability boundaries.

Mental model for a first-party Oclif command plugin as one host-composed terminal projection on public package boundaries.

Mental model for an application as the concrete selection and realization boundary of the product chain.

Mental model for inert reusable support that carries no product, runtime, or projection authority.

Mental model for projecting resolved Habitat applications into the Nx scheduler without acquiring policy authority.

Mental model for plugins as narrow projections of existing capability into one runtime role and surface.

Mental model for one concrete realization of a provider-neutral resource contract.

Mental model for a provider-neutral capability contract at the head of the Habitat product chain.

Mental model for AGENTS.md as a local navigation and boundary surface rather than architecture authority or project memory.

Frame a database as an optional service-owned persistence boundary that projects store capabilities through context.

Mental model for Grit patterns as semantic source relationships that complement structure without replacing types or behavior.

Mental model for one Habitat rule packet as one reviewable policy claim with one qualified verification mechanism.

Mental model for a public API server plugin as an operation boundary around one embedded service and one projected client.

Mental model for server plugins as server-hosted projections whose narrower surface kind owns the caller boundary.

Use when designing, setting up, planning, launching, running, reviewing, closing, or handing off a workstream. Trigger this for DRA-owned workstreams, agent waves, workstream records, proof boundaries, review loops, zero-context Next Packets, or workstream closure.

Use when designing or running workstream review loops, choosing review lanes, capturing findings, dispositioning accepted/rejected/waived work, and turning review results into repair demands or Next Packet entries.