Skip to main content

Eidos: Git-Native AI Software Development Ecosystem

CI PyPI Python Documentation Living Portal License: MIT

Eidos is an open, Git-native, agent-agnostic development framework designed to unify product definition, architectural invariants, and autonomous coding agents under executable living specifications.

This repository dogfoods the Eidos Specification Standard to define Eidos itself.


Quickstart

# Install globally as a standalone CLI tool with uv (recommended)
uv tool install eidos-ai

# Or install with pipx
pipx install eidos-ai

# Or run ephemerally without installing
uvx --from eidos-ai eidos --help

# Initialize Eidos in your repository (or use `eidos init --lite` for a 3-file starter profile)
eidos init

# Synchronize SQLite + FTS5 + AST knowledge graph index
eidos index sync

# Extract a token-budgeted architectural context slice for a file or task
eidos context -t "authentication and drift detection"

# Validate living specifications
eidos validate eidos

# Verify zero drift between code, tests, and living specs
eidos drift

# Launch interactive C4 architecture portal
eidos portal serve --path eidos --port 8080

# Install AI agent plugin (4 skills for Antigravity, Claude, Cursor, Copilot, Aider, Cline, OpenCode, Codex)
eidos plugin install all

Repository Architecture

eidos/
├── pyproject.toml                 # Modern Python package definition (eidos-ai on PyPI)
├── zensical.toml                  # Zensical documentation site configuration
│
├── src/eidos/                     # [THE ENGINE / SOLUTION]
│   ├── cli/                       # CLI commands (`eidos validate`, `eidos drift`, `eidos context`, etc.)
│   ├── core/                      # Spec parser, validator, scaffolder, DeltaEngine & knowledge graph (`index/`)
│   ├── plugin/                    # Agent plugin installer (`TargetAdapter`), validator, and lifecycle hooks
│   ├── portal/                    # Interactive Living Architecture server & static portal generator
│   └── vcs/                       # Git spec-to-code drift detection, AST symbol diffing & invariant verification
│
├── assets/                        # [BUNDLED SCHEMAS, SKILLS & PORTAL ASSETS]
│   ├── schemas/v1/                # 16 canonical JSON/YAML schemas + shared `common/defs.yaml`
│   ├── plugin_reference/          # Canonical `agent-plugins.org v1.0.0` bundle & 4 workflow skills
│   └── portal/                    # Pre-compiled air-gapped portal SPA (`bundle.html.gz`)
│
├── eidos/                         # [THE LIVING SPECIFICATION / DOGFOODED CATALOG]
│   ├── system.adoc                # Root system descriptor (SYS-*)
│   ├── personas/                  # Human & AI actor roles (PER-*)
│   ├── policies/                  # Non-negotiable architectural policies (POL-*)
│   ├── domains/                   # Bounded contexts (DOM-*) & capabilities with test-bound invariants (CAP-*, INV-*)
│   ├── architecture/              # Arc42/C4 architecture (ARCH-*), containers (CNT-*), components (CMP-*), contracts (CTR-*)
│   ├── design/                    # Multi-Design Systems (DS-*), W3C tokens, UI components (UIC-*), clients (CLT-*), screens (SCR-*), flows (FLOW-*)
│   ├── explorations/              # Hypothesis-driven technical spikes (EXP-*)
│   └── deltas/                    # In-flight and applied SpecDelta mutations (DLT-*)
│
├── docs/                          # User documentation site (Zensical)
└── tests/                         # Engine & invariant verification test suites

Key Distinctions from Existing Tools

Dimension Traditional / Existing Tools Eidos Approach
Scope Coding loop only (Aider, Claude Code) or monolithic bot (Devin) Full SDLC: Exploration → Product Baseline → SpecDelta → Code → CI
Specifications Ephemeral Jira tickets, stale Confluence/Notion pages Versioned YAML frontmatter + AsciiDoc living in Git
Change Management Narrative RFC essays that rot in archive folders Declarative SpecDelta mutations applied automatically upon merge
Agent Support Vendor-locked to a single proprietary LLM Agent-agnostic via agent-plugins.org v1.0.0 & CLI-first Agent Skills
VCS Support Tied to a single SaaS platform or closed web UI 100% Git-native local repository engine

Navigating the Specifications


Documentation & Living Portal


License

Licensed under the MIT License.

Metadata

Release files for eidos-ai 0.12.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for eidos-ai 0.12.1
File Size Uploaded Provenance
eidos_ai-0.12.1.tar.gz 2.3 MB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for eidos-ai 0.12.1
File Interpreter ABI Platform
eidos_ai-0.12.1-py3-none-any.whl Python 3 none any Details

Total release size: 4.0 MB

Release files / eidos_ai-0.12.1.tar.gz

Download URL eidos_ai-0.12.1.tar.gz
Size 2.3 MB
Tags Source
SHA-256 checksum
How to use checksums
3e67deeba9d5dd7305121208bf4446755653175cc4a4f0f7a1506a70d97c79d5
BLAKE2b-256 checksum
How to use checksums
82bf3a347e70f54efaa1c7146505a51add233b82422fada2ed642707b6227d81
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 19, 2026.

Transparency log

Release files / eidos_ai-0.12.1-py3-none-any.whl

Download URL eidos_ai-0.12.1-py3-none-any.whl
Size 1.8 MB
Tags Python 3
SHA-256 checksum
How to use checksums
9b59d092c9c9e75ea4ca014a42a15a82965dc2f84f45dc81d1bdfb42e3733b7c
BLAKE2b-256 checksum
How to use checksums
3c26920a511d8e3df9976d1ea4396e825a0a09689724026f2f04c273fc623e33
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 19, 2026.

Transparency log

Security for eidos-ai 0.12.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for eidos_ai-0.12.1.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 19, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page