THE PLATFORM

The operating substrate behind every Ennphasis engagement.

The platform is the system we build on, operate from, and hand over. It is what makes our work auditable, repeatable, and reversible — and what separates operating discipline from billable hours.

OPERATING PROOF

The substrate is built around four invariants.

Every capability in the platform inherits the same operating contract. Nothing runs without explainability. Nothing applies without an audit trail. Every action is reversible within a defined window. The operator always has the override.

web-builder / production route
Canonical route /platform/
Surface state production substrate
Explainability Every suggestion carries reason + snapshot_before. Every apply leaves an audit_log entry.

invariant

Reversibility Rollback within 90 days in one command. apply_*.py persists pre-state snapshots.

invariant

Human override Even with auto_apply on, the operator can pause or revert at any time.

invariant

Fail-safe defaults Without config, nothing runs. Ingest broken, the rule abstains rather than guesses.

invariant

Side-effect gate owner approval

Deploys, real sends, production writes and DNS mutations require explicit operator approval in chat. Evidence → draft → approval → apply → readback.

ENNPHASIS platform layer stack with audited operating pins

CAPABILITIES

Live capabilities — composable, all sharing the same substrate.

Each capability is a packaged module that activates a defined area of operating work. More capabilities are added to the platform as they reach production maturity; this page lists what is live today.

READ THE SUBSTRATE

Two complementary lenses on the platform.

Principles

Why the substrate is shaped this way. Event sourcing, audit_log, idempotency and reversibility — the operating contract that every capability inherits.

See service →

Integrations

Where the platform connects. SP-API, Ads API, GSC, Shopify and the other surfaces the platform reads, writes and audits.

See service →

NEXT

If your operation has reached the limits of spreadsheets and rule-of-thumb, the platform is what comes after.

Bring the friction: where decisions are made by gut today, where the same mistake repeats, where the team cannot explain what the system did last week. The conversation starts there.

Talk about the platform

Bring the friction you can already feel.

We will shape the route: pattern, system review, audit or no-build decision before anything expands.