GNO.SYS ☀️🌏💗🌐
Guardian Nexus OmniSanc Engineering Suite for Starting Yearround Sanctuary
Compound Intelligence Ecosystem Meta-Package - Install everything you need to run Isaac's compound intelligence system.
What is GNO.SYS?
GNO.SYS is a meta-package that installs and configures the complete compound intelligence ecosystem, including:
- Knowledge & Memory: CartON (knowledge graph), TOOT (context continuity), Brain Agent (distributed cognition)
- Navigation & Workflow: STARSHIP (flight configs), STARLOG (project tracking), Waypoint (learning journeys)
- Intelligence & Learning: GIINT (multi-fire intelligence), Opera (pattern learning), Canopy (execution tracking)
- Identity & Publishing: SEED (identity unification & publishing platform)
- Orchestration: STARSYSTEM (mission management), Metastack (structured outputs)
- Infrastructure: HEAVEN Framework, Emergence Engine, FlightSim
Installation
1. Install GNO.SYS
pip install gnosys
2. Install TWI Plugin (hooks/skills/commands)
# Manual installation
cp -r twi ~/.claude/plugins/
# Or if gnosys provides the plugin:
gnosys install-plugin # (future feature)
3. Initialize Configuration
gnosys init
This creates:
~/.gnosys/.env.example- Environment variable template~/.config/strata/servers.json.template- Strata MCP config template
4. Configure Environment
# Copy and edit environment variables
cp ~/.gnosys/.env.example ~/.gnosys/.env
nano ~/.gnosys/.env
Fill out required variables:
# GitHub
GITHUB_PAT=your_github_pat_here
REPO_URL=https://github.com/yourusername/private_wiki
# Neo4j
NEO4J_URI=bolt://localhost:7687
NEO4J_USER=neo4j
NEO4J_PASSWORD=password
# OpenAI
OPENAI_API_KEY=sk-proj-...
# Directories
HEAVEN_DATA_DIR=/tmp/heaven_data
LLM_INTELLIGENCE_DIR=/tmp/llm_intelligence_responses
CHROMA_PERSIST_DIR=/tmp/carton_chroma_db
# SEED Publishing
SEED_MEMBERSHIP_SITE_URL=https://your-seed-site.replit.app
SEED_MEMBERSHIP_SITE_API_KEY=your_api_key
SEED_MEMBERSHIP_SITE_ADMIN_EMAIL=admin@example.com
SEED_MEMBERSHIP_SITE_ADMIN_PASSWORD=your_password
# GIINT
GIINT_TREEKANBAN_BOARD=your_board_name
5. Start Neo4j (if not running)
docker run -d \
-p 7687:7687 \
-e NEO4J_AUTH=neo4j/password \
neo4j:latest
6. Configure Strata MCPs
gnosys configure-strata
This reads your .env file and generates ~/.config/strata/servers.json with all MCP configurations.
7. Add Strata to Claude Code Config
Manually add the Strata MCP server to your Claude Code configuration. Strata will orchestrate all other MCPs.
8. Restart Claude Code
Restart Claude Code to load all MCPs through Strata.
Verify Installation
gnosys status
Shows configuration status and Neo4j connection health.
Architecture
GNO.SYS follows a layered architecture:
User
↓
Claude Code + TWI Plugin (hooks/skills/commands)
↓
Strata (MCP Orchestrator)
↓
21 MCP Servers (CartON, STARSHIP, STARLOG, SEED, etc.)
↓
Supporting Libraries (pydantic-stack-core, payload-discovery, etc.)
↓
Infrastructure (Neo4j, ChromaDB, filesystem storage)
Component Overview
Core MCPs
- carton: Neo4j knowledge graph with wiki+ontology layers
- starlog: Project tracking and session management
- starship: Flight configs and navigation system
- waypoint: Progressive disclosure learning journeys
- STARSYSTEM: Mission management with fitness scoring
- seed: Identity unification and publishing platform
- giint-llm-intelligence: Multi-fire intelligence with response editing
- brain-agent: Distributed cognition for large contexts
- emergence-engine: 3-pass methodology (Conceptualize → Generally Reify → Specifically Reify)
- opera: Pattern learning and workflow capture
- canopy: Execution tracking
- toot: Context continuity breadcrumbs
- flightsim: Flight execution engine
- metastack: Renderable Pydantic models for structured outputs
- llm2hyperon: Hyperon/MeTTa integration for computational metagraphs
- heaven-framework-toolbox: Registry, OmniTool, NetworkEditTool
Supporting Libraries
- pydantic-stack-core: Stackable, renderable Pydantic models
- payload-discovery: Systematic agent learning framework
Troubleshooting
Neo4j Connection Failed
# Start Neo4j container
docker run -d -p 7687:7687 -e NEO4J_AUTH=neo4j/password neo4j:latest
# Check connection
gnosys status
MCPs Not Loading
- Verify Strata config:
cat ~/.config/strata/servers.json - Check .env values:
cat ~/.gnosys/.env - Restart Claude Code
- Check Claude Code logs
Missing Environment Variables
gnosys configure-strata
# Will show which variables are missing
Development
Installing from Source
git clone https://github.com/yourusername/gnosys
cd gnosys
pip install -e .
Running Tests
pip install -e ".[dev]"
pytest
Philosophy
GNO.SYS embodies the compound intelligence philosophy:
- Compounding Value: Each system interaction creates incremental, sustainable value
- Cognitive Separation: Internal thinking vs external communication (GIINT)
- Systematic Learning: Structured curricula and progress tracking (Payload Discovery)
- Knowledge Publishing: Transform private work into public knowledge (SEED)
- Anti-Hallucination: Complete context understanding before modifications (Context Alignment)
License
MIT
Support
- Issues: https://github.com/yourusername/gnosys/issues
- Docs: https://docs.sanctuary.systems (future)
☀️🌏💗🌐 - The World Incorporated, a Sanctuary Bastion
Metadata
Release files for gnosys 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| gnosys-0.2.0.tar.gz | 12.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| gnosys-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 23.4 kB
Release files / gnosys-0.2.0.tar.gz
| Download URL | gnosys-0.2.0.tar.gz |
|---|---|
| Size | 12.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
af21c7d78dbde3c79ed9c05edf37fe5e249ff8b844458a9df7f71c12847126b3
|
|
BLAKE2b-256 checksum How to use checksums |
d3fb88f42a92a7e84214b1b86b6fcc94e7e9d59aeb7f49f818d960023801a24f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.6
|
Release files / gnosys-0.2.0-py3-none-any.whl
| Download URL | gnosys-0.2.0-py3-none-any.whl |
|---|---|
| Size | 11.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9a0b8c1194cc932360e1dc806e320933963e082471d40b8e51467367878ee5af
|
|
BLAKE2b-256 checksum How to use checksums |
8ee394de5772262289ce9d65ca1036cb0cb421f2eaf2809c9bd96b885402bca4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.6
|
Security for gnosys 0.2.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
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.