Skip to content
NRM

ENGINEERING DISCIPLINE

The Operating Model

How every NRM platform is built and kept in production: separate surfaces with separate permissions, a read-first gate, rules in the repository, and verification against production before anything closes.

Platform architecture diagram
1

Pillar 1

Three-surface operating model.

Coordination (plan, scope, draft), Execution (scoped code changes, migrations, deploys), and Background (autonomous overnight audits and scheduled jobs) run as separate surfaces with separate permissions. Routing work between them — and deciding what never leaves human review — is the architecture; the model vendor is interchangeable.

2

Pillar 2

Read-first gate.

Execution agents cannot see coordination context, so every change is gated on reading the canonical standards docs first and verifying against the documented contract before proposing anything.

3

Pillar 3

Rules library, not prompts.

Roughly 70 cross-referenced operational rules — captured from real incidents (data-safety rules, dedup/idempotency contracts, deploy conventions) — are enforced as standing instructions in the repository. New sessions inherit the discipline instead of re-learning it.

4

Pillar 4

Verification over self-report.

No task closes on an agent's claim. Completion means browser verification and database checks against production, with scraper runs, pipeline stages, and sends logged to audit tables.

5

Pillar 5

Business method in the loop.

The same discipline runs the revenue side: a documented outbound methodology (HIT-AIM™) layered into an AI workflow, measured by stranger-to-engaged conversion rather than activity counts.

Governance posture

Scoped permissions per surface. Audit trails on every operation that touches production data. RLS-enforced data boundaries. Deployment gates on security scans. Secret scanning on every commit as a standing release discipline. Third-party audit as a standing release gate. The security posture isn't a one-time sweep — it's the shape of the delivery pipeline.

This operating model is the platform's standing documentation. It is how MaineCoastLife.com stays reliable in production under SLA.