Metadata-Version: 2.4
Name: synoi
Version: 0.0.1
Summary: Reserved name held by SynOI Inc. Not a functional package. See https://synoi.systems
Author-email: "SynOI Inc." <hello@synoi.systems>
License: Apache-2.0
Project-URL: Homepage, https://synoi.systems
Classifier: Development Status :: 1 - Planning
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: Apache Software License
Classifier: Programming Language :: Python :: 3
Requires-Python: >=3.9
Description-Content-Type: text/markdown

# synoi

**This name is reserved by SynOI Inc. It is a placeholder, not a functional package.**
Installing it does nothing. It exists so that nobody else can publish under it.

## Why this exists

PyPI has a flat namespace with no organisation scoping. On npm, `@synoi/*` is a scope
only SynOI can publish into. PyPI has no equivalent, so every unclaimed `synoi`-prefixed
name can be registered by anyone, and anything published under one would appear to come
from SynOI.

That matters most for security-adjacent tooling: a package that sits in an agent's
tool-call path sees every call and reads operator credentials by design, so a hostile
package under a trusted name would not look anomalous.

## Where the real software is

SynOI's libraries currently publish to **npm**, not PyPI:

- `@synoi/sraid` — canonicalisation and signed-object primitives
- `@synoi/gap` — Governed Agent Protocol types
- `@synoi/sdk` — the `gate()` wrapper

The one functional SynOI package on PyPI is:

- `synoi-hermes-guard` — governance hook for the Hermes agent framework

If this placeholder is ever replaced by a real package, it will be announced at
https://synoi.systems first.

## Contact

hello@synoi.systems
