Lophiarch
v2.2.2Policy-gated AI reconnaissance with Telegram ChatOps, MCP orchestration, disposable scanner workers, and PDF reporting.
The library
One timeline, every project
Ordered by when each repository was created. Documented projects link straight to their manuals; the rest point to the source until their documentation is worth reading.
- Stable
- Concept
Catapult
ConceptA local safe storage layer for API keys and reusable capabilities. Repository exists; the product is not running yet.
Repository onlySource ↗ - Pre-alpha
SCRYMR
Pre-alphaA Discord-native community security and incident-response sentinel built around human approval and calm response.
Repository onlySource ↗ - Experimental
Parabiont Protocol
v0.1.2A signed, leased context-carrier profile over A2A. Approved state moves between agents without becoming an unpoliced memory dump.
- Experimental
Axionorm
v0.1.0YAML-first policy for agent context and authority, evaluated through a real OPA/Rego backend with fail-closed behavior.
- Design
Lophiont
Design stageThe planned parabiotic carrier connecting Lophiarch to external agents and graph systems. Not implemented yet.
Repository onlySource ↗ - Available
Discord AI Notifier
AvailableA reusable Discord notification plugin that runs on your own bot token and channel, with hosted and local providers.
Repository onlySource ↗ - Experimental
PARALAX MCP
v0.1.2Policy-gated MCP tools and desktop integration that connects Axionorm and Parabiont to a working agent session.
Where to start
Read by what you need to do
Run
Security operations
Reconnaissance with an operator gate, declared scope, and policy-checked tool calls before anything reaches a target.
Lophiarch docs →GovernAgent authority
YAML-first policy for what an agent may read, which tools it may call, and how much context leaves a session.
Axionorm docs →CarryGoverned context
A signed, leased carrier for moving approved state between agents, plus a policy-gated MCP gateway on the receiving side.
Parabiont docs →Documentation is reviewed like code
Every page here lives in Git and is reviewed like code. Commands, environment variables, and policy behavior are checked against the source, not copied from a slide. If a page disagrees with the code, the code wins and the page gets fixed.