HomeOpen source1 project · Apache-2.0

Open source at Sigrix

The parts of this platform that other people have to build against, we publish. A marketplace can be a product; the contract an agent is run and licensed under should not be one. So the protocol under Sigrix is drafted in the open, under a licence anyone can use, with the specification as the thing everybody pins to rather than our implementation of it.

Explore Postern → GitHub organisation

Projects

1 · Postern

License

Apache-2.0

Status

0.1 · draft

Organisation

sigrix-io

Projects

What we maintain

One project today. It is the one everything else on the platform sits on.

github.com/sigrix-io ↗

Specification v0.1 · draft Apache-2.0

Postern

The open execution and entitlement protocol for packaged AI agents.

You bought or downloaded an agent. It is a folder on your machine. Now what? Today the answer is different for every agent, so every client that wants to offer something nicer than a terminal has to hard-code that knowledge per agent — which means nobody does it. Postern fixes the interface, not the agent: four HTTP verbs an agent serves, and a licensing check the packaging standards leave as metadata only.

Project page → Read the specification GitHub ↗

Repositorysigrix-io/postern

Specification0.1 · draft

LicenseApache-2.0

Reference impl.Sigrix · Level 3

InstallDocker · pip

describerunstreamstatus

How we work in the open

Three commitments

The document is what you pin to

Sigrix runs a Postern implementation, but the specification is the definition. Where the two appear to disagree, the document wins and the disagreement is worth an issue.

Published before it is finished

Feedback is cheapest while changing things is still free, and that is only true if everyone knows it is still true. The specification is not tagged, and we say so on every page.

No dependency in either direction

A distributor is optional, the schemas work without ever being fetched, and the Sigrix profile is one any implementer may ignore. Nothing in the protocol requires our services.

Everything we publish lives in one organisation

Issues and pull requests are read there. It is the only community surface we run today.

github.com/sigrix-io Open on GitHub ↗