Every major Smplify release gets a plate: a monochrome drawing, generated from code, published alongside the release. This is Plate 003, and unlike the two before it, this one is a map of the whole platform rather than a single launch.

It exists because of a problem with roadmap slides. A roadmap can put "coming soon" next to anything, forever, and nothing about the slide forces the claim to be true. A plate cannot do that. Either an arc is drawn solid or it is not. So we drew everything we have built as one instrument, and we let the drawing carry the status.

§ 01 · How to read it

Every mark maps to something real. Nothing on the plate is ornament, and nothing is there because the composition needed filling. The solid dot at the centre is the control plane: one point, three fine rings, and everything else radiates from it. That is the actual architecture, not a metaphor.

That vocabulary is inherited. On Plate 001 the same three textures carried macOS, Windows and Linux. Here they carry maturity instead. One vocabulary, reused rather than reinvented, which is the point of having a system at all.

The spokes are gates

Each spoke crosses the instrument from the control plane outward, and each carries a small square where it crosses. Those are approval gates. They sit on the spoke rather than beside it because that is where the enforcement lives: on the execution path, inside the platform, where no client can route around it by changing channel. Look closely and one square carries two bars where the others carry one. That is two-person control, the same glyph we used on Plate 001. We do not explain that one on the plate.

The tick ring is telemetry, and the dial is your SIEM

Ninety-six ticks around the perimeter, every eighth one heavier. Every privileged action on the plane leaves as open-schema telemetry, including the denials. The small dial outside the instrument, marked READ, is the reader: your SIEM, your analyst, your AI-SOC. The hatched beam between them is marked EMIT. The dial sits outside the plane on purpose. Smplify emits, and does not own the reasoning.

And there is a message in it

The heavy broken band around the outer edge is Morse, read clockwise from the small triangle at twelve. It is two words. It is not a slogan, it is a claim, and it is the same claim the drawing makes structurally. We verify these by decoding them back out of the finished image rather than trusting the code that drew them, because the people who bother to decode it are exactly the people we are trying to reach. First correct decode gets the next plate early.

§ 02 · Sect I · what is solid

Fourteen arcs, drawn continuous. Shipped and running today. Count them clockwise from the sector's start marks and they read in this order:

1. Apple Declarative Device Management
2. ADE and ABM zero-touch enrollment
3. Configuration profiles
4. VPP app management
5. Account-driven BYOD enrollment
6. Approval Gates, enforced on the execution path
7. Privilege-grade RBAC with custom roles
8. Multi-tenant partner to customer hierarchy
9. OCSF telemetry egress to your own SIEM
10. MCP gateway, tenant and role scoped
11. Endpoint security connector on Apple ESF
12. CIS, DISA STIG and NIST compliance baselines
13. Whitelabel branding and custom domains
14. CLI and configuration as code

§ 03 · Sect II · what is dashed

Three arcs, drawn as short dashes. Built, running internally, rolling out. We are not calling these generally available until they are deployed, and you should hold us to that distinction:

1. Windows MDM: enrollment, CSP profiles, BitLocker, Defender, MSI deploy
2. Linux hardening engine with drift auto-remediation
3. Third-party app catalog, signed and notarized

On Linux specifically: this is not agent scripting with a dashboard on top. It is a curated hardening engine covering firewall, SELinux and AppArmor, SSH, auditd, PAM, disk encryption and kernel parameters, with drift auto-remediation and approval gating. It is also new, and we are not going to claim it is battle-tested at scale yet.

§ 04 · Sect III · what is dotted

Eight arcs, drawn as scattered dots. Specified and designed, not built. Named here without dates on purpose, because a date we have not committed engineering to is just a roadmap slide with better typography:

1. Rewind: configuration versioning and rollback
2. Lighthouse: AI agent discovery and governance
3. Foreman: outcome orchestration layer
4. Managed Device Attestation
5. FileVault recovery key escrow
6. Directory integration through SCIM and OIDC SSO
7. Shared iPad, tvOS, watchOS, visionOS
8. Android

Android is on that list as a specification only. Today we are focused on Apple, Windows and Linux, and we are not claiming an Android capability we do not have.

§ 05 · Why publish it this way

Because the audience we care about does not read marketing pages, it reads endpoints. MSP owners, security leads and platform engineers evaluate by finding the gap between what a vendor says and what a vendor ships, and they are very good at it. Publishing the gap ourselves, in a form that cannot hedge, is cheaper than being caught in it.

Either the arc is solid or it is not.

THE PLATE CANNOT HEDGE · THAT IS THE POINT

It is also a forcing function. Next release, some of those dotted arcs have to be dashed, and some of the dashed ones have to be solid, and the plate will show plainly whether that happened.

If you run a fleet, the plate is also a planning tool. The solid sector is what you can put in front of an auditor today. The dashed sector is what to pilot now so it is boring by the time it is GA. The dotted sector is what to hold us to, and the right question at any demo is which arc moved since the last plate.

§ 06 · The series

Plate 001 was the study of convergence, for the platform release. Plate 002 was the study of delegation, the note that named Agentic Device Management as a discipline. This is Plate 003, the study of accumulation. Each is generated from code rather than drawn in a design tool, which is why the tick counts, the Morse timing and the alignment are exact rather than eyeballed. The generator for each plate is kept, so any of them can be re-rendered or resized without being rebuilt.

Smplify is a headless, governed device control plane. If you want to see the parts that are solid, the API documentation is public and the MCP gateway is live.

FIELD NOTE 003 · THE STUDY OF ACCUMULATION · 08 2026