Skip to content
Planning workspace
Inkfire Platform

Engineering Blueprint

This is the engineering drawer, not the team entry point.

The planning workspace keeps technical detail available without making every staff member decode cryptography before giving useful feedback.

Non-negotiable build rules

Core is the source of truth

Billing, plans, contracts, tickets and policy live centrally.

Async by default

External calls and long work go to background jobs; UI receives immediate acknowledgement.

Outbound-only SiteKit

No inbound remote management endpoint on a client WordPress site.

Separate client/staff surfaces

Portal cannot contain internal controls; Frontdesk cannot borrow client authentication.

Modules fail independently

A specialist capability can be disabled or quarantined without sinking the platform.

AI works through abilities

No direct database access. Mutating actions are permissioned, auditable and approval-gated.

Build sequence

Architecture first, remote superpowers later.

1

Foundation

Core bootstrap, migrations, module registry, RBAC, tenant scope, audit, OpenAPI, queues and health.

2

Business MVP

Clients, contacts, Service Desk, projects/tasks, time tracking and client plans.

3

Integrations

Microsoft identity, Xero, NinjaOne, migration tooling and automation.

4

SiteKit & WebOps

Outbound-only agent, telemetry, signed command queue, update orchestration and diagnostics.

5

Hardening

Sentinel, AI-assisted recovery, module quarantine, performance, security and pilot rollout.