Skip to content

docs: add AEGIS (@stackbilt/aegis-core) to docs site and sync manifest #11

@stackbilt-admin

Description

@stackbilt-admin

Context

AEGIS (aegis-oss) has transitioned from an internal-only tool to @stackbilt/aegis-core — a publishable open-source framework that anyone can install and extend. The docs site needs to reflect this.

What needs updating

1. docs-manifest.json — Add aegis-oss as a sync source

"aegis": {
  "repo": "aegis-oss",
  "pages": {
    "aegis.md": {
      "source": "docs/architecture.md",
      "section": "ecosystem",
      "order": 2,
      "color": "#8b8bff",
      "tag": "02"
    }
  }
}

The aegis-oss repo has 5 docs files ready:

  • docs/getting-started.md — Deploy your own instance
  • docs/architecture.md — Cognitive kernel design
  • docs/configuration.md — Operator config reference
  • docs/memory-system.md — Memory tiers and dreaming cycle
  • docs/connecting-mcp-clients.md — MCP client setup

2. ecosystem.md — Update AEGIS description

Current (line ~31):

| **AEGIS** | `aegis.stackbilt.dev` | Internal cognitive agent — memory, goals, task pipeline |

Should be:

| **AEGIS** | `aegis.stackbilt.dev` | Open-source cognitive agent framework (`@stackbilt/aegis-core`). Multi-tier memory, autonomous goals, dreaming cycle, MCP native. [GitHub](https://github.com/Stackbilt-dev/aegis-oss) |

Also add AEGIS to the ecosystem overview alongside Charter:

| **AEGIS** (`@stackbilt/aegis-core`) | Open-source (Apache-2.0). Persistent AI agent framework for Cloudflare Workers. Deploy standalone or extend as a dependency. |

3. New page: aegis.md (optional but recommended)

A dedicated AEGIS page covering:

  • What it is (persistent AI agent framework)
  • Two consumption modes (standalone vs dependency)
  • createAegisApp() composition pattern
  • Extension interfaces
  • Link to aegis-oss repo

4. .bak cleanup

CLAUDE.md.pre-adf-migrate.bak exists in the docs repo root — delete it.

References

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions