Reference blueprints, not demos.
Enterprise IT does not trust unmanaged edge software, and it should not. Every entry in this library ships as a pair: working code running on local silicon, and the governance write-up that makes it deployable.
The format every blueprint follows
The left half is the implementation: what the agent does, which local models it runs, what hardware it was measured on. The right half is the part most demos skip: how the agent loop is isolated in its execution container, how identity is handled through your directory, how the device is managed by your endpoint tooling, and how data handling maps to your compliance labels. The seven control questions (identity, data, actions, location, logging, escalation, revocation) are answered in writing for every entry.
What publishes here
The library opens with the practice, regulated knowledge work first. Each blueprint publishes only after it clears the same governance bar we would hold a client deployment to. Nothing here will ever be a mockup: if the page says the workload ran locally, it ran locally, and the write-up says on what.
Until the first entries land, the placement model is the working proof of how the practice does math in public.