How enforcement adapts

Novarch governs any consequential write you can write a rule for. You attach whatever evidence your workflow produces, author rules in plain English over it, and the Novarch engine enforces them across the whole session. Accounts Payable and Customer Support ship as batteries-included starter packs, a fast start and a worked reference, not the boundary of what Novarch governs.

The model is three decisions

1. Pick an action_type. A short, stable string that names the consequential write ("process_invoice", "issue_refund", "grant_access", "export_dataset"). It is the join key between your writes and your rules.
2. Attach evidence. Build a context object in the write’s context_builder. Use a typed context when your workflow is AP or CS; use GenericContext with an open bucket of fields for anything else. The Novarch engine reads whatever you attach.
3. Author rules over it. In the platform dashboard’s RULES tab, write plain-English rules scoped to your action_type. The Novarch engine applies them to every matching write and cites the rule and the evidence on every paused or blocked action.

Starter packs, not the ceiling

AP and CS bundle a typed context, tuned signal extractors, and a default rule pack for one common vertical. Adopt a pack as-is, edit its rules, or ignore it. If your workflow does not match a pack’s shape, you are not missing anything: reach for Custom workflows and author rules over your own evidence. Same engine, same rules, same auditable Decision.

Where to go next

• Custom workflows: the general case, with a worked access-provisioning example.
• Rules: author the plain-English rules that gate your action_type.
• Accounts Payable and Customer Support: the two bundled starter packs.