memory-api

memory-api is the repository that exposes the core crates and operator surfaces behind rules, specs, tickets, and audits.

Direct child READMEs and the ticket crate manifest:

• tools/cli/rule-cli/README.md
• tools/cli/spec-cli/README.md
• crates/ticket/Cargo.toml
• tools/cli/audit-cli/README.md
• tools/http/spec-http/README.md
• crates/ticket/Cargo.toml (ticket-http configuration)
• tools/mcp/rule-mcp/README.md
• tools/mcp/spec-mcp/README.md
• crates/ticket/Cargo.toml (ticket-mcp configuration)
• tools/mcp/audit-mcp/README.md

Installable and executable surfaces in this repository include the rule, spec, ticket, and audit CLIs, the rule-mcp, spec-mcp, ticket-mcp, and audit-mcp MCP servers, and the spec-http and ticket-http HTTP binaries.

Tool Surface

Crate or surface	What it is used for	Typical entry points
memory-api	Generic filesystem-backed entity storage, schema validation, SQLite indexing, search, edge management, and board coordination.	Reused by the other crates in this repo.
rule-api	Canonical rule manifests, markdown import, target composition, and nested workspace discovery.	rule, rule-mcp
spec-api	Specification manifests, sections, slugs, code references, and validation rules.	spec, spec-mcp, spec-http
ticket-api	Ticket domain logic, workspace state, board snapshots, execution contracts, watchers, and reconciliation.	ticket, ticket-mcp, ticket-http, ticket-vscode
audit-api	Repository quality audits, indexes, summaries, and review-oriented validation flows.	audit, audit-mcp

Dependency Graph

flowchart LR
    subgraph Shared
        Memory[memory-api]
        Viewer[viewer-api]
    end

    subgraph Domain
        Rule[rule-api]
        Spec[spec-api]
        Ticket[ticket-api]
        Audit[audit-api]
    end

    subgraph CLI
        RuleCli[rule-cli]
        SpecCli[spec-cli]
        TicketCli[ticket]
        AuditCli[audit-cli]
    end

    subgraph MCP
        RuleMcp[rule-mcp]
        SpecMcp[spec-mcp]
        TicketMcp[ticket-mcp]
        AuditMcp[audit-mcp]
    end

    subgraph HTTP
        SpecHttp[spec-http]
        TicketHttp[ticket-http]
    end

    Rule --> Memory
    Spec --> Memory
    Ticket --> Memory

    RuleCli --> Rule
    RuleCli --> Memory
    SpecCli --> Spec
    SpecCli --> Memory
    TicketCli --> Ticket
    TicketCli --> TicketHttp
    AuditCli --> Audit

    RuleMcp --> Rule
    RuleMcp --> Memory
    SpecMcp --> Spec
    SpecMcp --> Memory
    TicketMcp --> Ticket
    AuditMcp --> Audit

    SpecHttp --> Spec
    SpecHttp --> Memory
    SpecHttp --> Viewer
    TicketHttp --> Ticket
    TicketHttp --> Viewer

Loading

Tool Use Examples

Install the CLI tools

From the context-engine repo root, the shared installer can run the same four Cargo installs for you:

bash ./install-tools.sh --tool rule-cli --tool spec-cli --tool ticket --tool audit-cli

If you are working directly from a memory-viewers/memory-api checkout instead of the repo root, run the underlying install commands from this workspace:

cargo install --path tools/cli/rule-cli --bin rule
cargo install --path tools/cli/spec-cli --bin spec
cargo install --path crates/ticket --bin ticket --features cli
cargo install --path tools/cli/audit-cli --bin audit

After that, verify the install with rule --help, spec --help, ticket --help, and audit --help. The command-specific docs live in tools/cli/rule-cli/README.md, tools/cli/spec-cli/README.md, the ticket crate manifest, and tools/cli/audit-cli/README.md. The ticket crate exposes ticket, ticket-mcp, and ticket-http behind the cli, mcp, and http features respectively.

Set up a workspace repository

From the repository root, just run the tools. They discover an existing .rule, .spec, or .ticket by walking up from the current directory, and if none exists yet they initialize a local one in the current repository and seed a folder-local .gitignore for generated index files.

rule list
spec list
ticket board show
audit run .

When you add the first rule, spec, or ticket, the canonical rules/, specs/, and tickets/ folders are created automatically inside those local tool roots.

• rule list and rule sync-targets ... are documented in tools/cli/rule-cli/README.md.
• spec list and spec refs <spec-id> validate are documented in tools/cli/spec-cli/README.md.
• ticket board show is provided by the ticket crate's cli feature.
• audit run . is documented in tools/cli/audit-cli/README.md.

Common repo-local tasks

rule sync-targets --config rule-targets.yaml
spec refs <spec-id> validate
ticket board show
audit run .

• Regenerate repo docs from canonical rule content managed by rule-api.
• Validate a specification's code references through spec-api tooling.
• Inspect active board state through the ticket-api command surface.
• Run repository-level audits through audit-api.
• The HTTP command surfaces live in tools/http/spec-http/README.md and the ticket crate's http feature.
• The MCP command surfaces live in tools/mcp/rule-mcp/README.md, tools/mcp/spec-mcp/README.md, the ticket crate's mcp feature, and tools/mcp/audit-mcp/README.md.