# Matrix > Documentation for Matrix. ## Documentation - [Introduction](https://docs.matrixmcl.com/introduction.md): Matrix is the cognition and UX layer on Paxeer Network — it turns natural language into typed, inspectable, replayable agent execution across two rails: Neo and the MCL pipeline. - [Quickstart](https://docs.matrixmcl.com/quickstart.md): Clone matrix-core, build the nine Go modules, compile your first intent, drive an end-to-end walk, and run the per-user daemon. - [Core Concepts](https://docs.matrixmcl.com/concepts.md): The mental model behind Matrix — intents and frames, the closed verb and object vocabularies, cortex memory, skills, envelopes, attestation, and the replay invariant. - [Glossary](https://docs.matrixmcl.com/glossary.md): Definitions for the core Matrix terms — rails, intents, frames, cortex, skills, envelopes, attestation, MCP, PAX, and the deployment surfaces. - [Chatting with Matrix](https://docs.matrixmcl.com/user-guide/chat.md): How everyday conversation works — Neo as the front door, the Liaison narrator, when work is escalated to the rigorous MCL rail, and what the live transcript shows you. - [Using Skills](https://docs.matrixmcl.com/user-guide/skills.md): What skills are from a user's perspective — packaged capabilities the agent draws on, how they shape clarifying questions, and how correction works. - [Wallet & PAX](https://docs.matrixmcl.com/user-guide/wallet.md): How paid work is metered — PAX as the usage unit, the credit ledger, the free tier, agent balances on LayerX, and spend caps that keep on-chain work safe. ## Developer - [Architecture](https://docs.matrixmcl.com/developer/architecture.md): The layered Matrix model — MCL compiler, cortex memory, bridge, executor walker, and the surrounding service modules — plus the cross-cutting compile / execute / replay flows. - [MCL & Skill Authoring](https://docs.matrixmcl.com/developer/mcl.md): The MatrixScript compiler pipeline and how to write a SKILL.mtx — required sections, the §PROCEDURE on-blocks, slot resolution, unknowns, and validation. - [Cortex](https://docs.matrixmcl.com/developer/cortex.md): Cortex is the per-actor typed memory graph on Pebble — append-only journal, 9-type taxonomy, salience, embeddings + HNSW, Merkle snapshots, and the load-bearing replay invariant. - [Executor](https://docs.matrixmcl.com/developer/executor.md): Where intents become work — the lifecycle state machine, the pluggable plan walker, MCP tool dispatch, the materiality classifier, and the single-flight per-user daemon. - [Neo Runtime](https://docs.matrixmcl.com/developer/neo.md): Neo's recursive tool-calling loop — the transcript-as-state design, two-model architecture, context budget and compaction, the recovery ladder, and how it escalates to MCL. - [Determinism & Replay](https://docs.matrixmcl.com/developer/determinism-replay.md): The byte-identical replay invariant that makes Matrix auditable — canonical encodings, the D11 compilation seed, DropDerived/Rebuild, and the replay-invariant CI gate. - [Build, Test & Lint](https://docs.matrixmcl.com/developer/build-test-lint.md): The root Makefile workflow — building the Go modules, running race tests, the local CI gate, and golangci-lint setup. - [Contributing](https://docs.matrixmcl.com/developer/contributing.md): Ground rules, branching and conventional commits, quality gates, per-module conventions, and the design-change process for landing a PR in Matrix. - [Deployment](https://docs.matrixmcl.com/developer/deployment.md): How Matrix runs in production — the per-user daemon image, Fly Machine provisioning via the router, the shared-services box, and the browser/chronos/deus service images. ## API Reference - [API Overview](https://docs.matrixmcl.com/api-reference/overview.md): How Matrix HTTP surfaces are organized — the per-user daemon, the metered gateway, the router front door, and the agent-facing services (Chronos, Deus, LayerX, UWAC, Tachyon) — plus the shared auth patterns. - [Daemon API](https://docs.matrixmcl.com/api-reference/daemon.md): The per-user Matrix daemon (mcl-execute daemon) HTTP + SSE surface — chat, message submission, the events transcript stream, intent envelope chains, and identity. - [Gateway API](https://docs.matrixmcl.com/api-reference/gateway.md): The metered, OpenAI-compatible LLM proxy — chat completions and embeddings, priced per model against a versioned PAX rate card and debited from a per-user credit ledger. - [Router API](https://docs.matrixmcl.com/api-reference/router.md): The public front door — validates a Supabase JWT, wakes the user's Fly Machine, and reverse-proxies to their daemon. Plus the internal admin and wake surfaces. - [Chronos API](https://docs.matrixmcl.com/api-reference/chronos.md): The centralized agent scheduler — agent DID authentication plus create, list, get, and cancel alarms that wake an agent at a scheduled time. - [Deus API](https://docs.matrixmcl.com/api-reference/deus.md): The agent-service marketplace — discovery and catalog, the service registry lifecycle, quoting and metered invoke, payment channels, vouchers, receipts, and developer dashboards. - [LayerX API](https://docs.matrixmcl.com/api-reference/layerx.md): The settlement fabric — agent DID auth plus balance, deposit, pay, receipt, withdraw, and settle endpoints over the reserved-balance agent account model. - [UWAC API](https://docs.matrixmcl.com/api-reference/uwac.md): Universal Web Agent Connector — agent DID auth plus connect/callback/disconnect for the OAuth vault and a unified invoke surface for per-user external tools. - [Tachyon API](https://docs.matrixmcl.com/api-reference/tachyon.md): The agent-native Solidity/EVM engine — compile, test, simulate, deploy, and call contracts; manage chains and artifacts; plus a JSON-RPC endpoint and MCP surface. - [CLI Reference](https://docs.matrixmcl.com/api-reference/cli.md): The Matrix command-line surfaces — mclc, mcl-execute, mcl-tools, mcl-validate, cortex-shell, deusctl, and neo — and what each subcommand does. ## MCP - [MCP Overview](https://docs.matrixmcl.com/mcp/overview.md): How Matrix uses the Model Context Protocol — DID-bound agent manifests, the matrix:// tool URI scheme, stdio/http transports, the exhaustive-tools bijection check, and credential refs. - [Agent Manifests](https://docs.matrixmcl.com/mcp/agent-manifests.md): The JSON-on-disk agent manifest format — schema_version, agent DID, allowed_side_effects, the servers array with transport/command/args/env/package_digest/version/tools, and the locked design rules. - [Tool-Server Catalog](https://docs.matrixmcl.com/mcp/tool-servers.md): The MCP servers the default Matrix agent ships with — filesystem, fetch, web-search, browser, tachyon, deus, chronos, git, exec, media, paxeer-net, and uwac — and what each provides. - [Writing a Tool Bridge](https://docs.matrixmcl.com/mcp/writing-a-tool-bridge.md): Add a new MCP server to a Matrix agent — declare the server in the manifest, enumerate its tools exhaustively, pin the package digest, wire credentials, and verify the bijection. - [Server Templates](https://docs.matrixmcl.com/mcp/server-templates.md): The mcp-server-templates.json catalog — ready-to-copy MCP server definitions for popular integrations like GitHub, Supabase, Playwright, Cloudflare, and more. ## Reference - [Cortex: Developer Reference](https://docs.matrixmcl.com/reference/cortex/overview.md): Cortex is Matrix's per-actor persistent memory store — a Pebble-backed KV database with a typed taxonomy, salience-ranked queries, async embeddings, Merkle snapshots, and a full replay invariant. - [Store & Journal](https://docs.matrixmcl.com/reference/cortex/store-and-journal.md): The per-actor Pebble database, atomic write-batch machinery, key encoding, and the append-only journal that anchors cortex replay. - [Memory Taxonomy](https://docs.matrixmcl.com/reference/cortex/memory-taxonomy.md): The 9 typed memory kinds, the shared Head + Version layout, the three render Forms, and Tombstone semantics — the type system every other cortex subsystem operates on. - [Write API](https://docs.matrixmcl.com/reference/cortex/write-api.md): Package matrix/cortex exposes four mutating primitives: Write, Update, Tombstone, and UpdateHead. Every call commits an atomic Pebble batch containing the canonical record chang... - [Find Query](https://docs.matrixmcl.com/reference/cortex/find-query.md): Package matrix/cortex/query implements the typed Find query engine described in §12. cortex.Find is a thin facade that resolves near-vectors and delegates to query.Run. The engi... - [Context Bundle](https://docs.matrixmcl.com/reference/cortex/context-bundle.md): cortex.Context is the cold-start memory composer — the entry point an agent calls to hydrate its working memory at the beginning of a task. It returns a structured Bundle carryi... - [Embedder & Vector](https://docs.matrixmcl.com/reference/cortex/embedder-and-vector.md): matrix/cortex ships an async embedding pipeline built on a pure-Go HNSW vector index. Writes complete in one round-trip — the embedder is a separate goroutine tailing the journa... - [Edges & Graph](https://docs.matrixmcl.com/reference/cortex/edges-and-graph.md): cortex.AddEdge, cortex.RemoveEdge, and cortex.GetEdge manage typed directed edges between memories. cortex.IterEdgesOut / cortex.IterEdgesIn scan adjacency lists. query.Run with... - [Snapshot & Proofs](https://docs.matrixmcl.com/reference/cortex/snapshot-and-proofs.md): cortex/snapshot manages the cryptographic commitment layer: a journal MMR (Merkle Mountain Range) over every write, per-namespace SMTs (Sparse Merkle Trees) over canonical memor... - [Salience](https://docs.matrixmcl.com/reference/cortex/salience.md): Package matrix/cortex/salience computes and persists the per-memory ranking signal. Every memory has a Score record stored at salience/ that tracks the factor inputs. The li... - [Attest & Compact](https://docs.matrixmcl.com/reference/cortex/attest-and-compact.md): cortex.Attest records the outcome of a completed intent and feeds that outcome back into the salience of every memory the plan cited. cortex.Compact runs budget-aware context co... - [Scope](https://docs.matrixmcl.com/reference/cortex/scope.md): Package matrix/cortex/scope is the cryptographic privacy boundary for cortex reads and writes issued by sub-agents. A CortexScope binds a sub-agent's identity to a pinned snapsh... - [Replay](https://docs.matrixmcl.com/reference/cortex/replay.md): Package matrix/cortex/replay implements the cortex replay invariant: drop every derived index and rebuild it deterministically from the canonical journal. cortex.Rebuild is the... - [MCL Developer Documentation](https://docs.matrixmcl.com/reference/mcl/overview.md): The Matrix Communication Layer (MCL) is the compiler and protocol backbone of Matrix. Every user interaction starts here: natural language goes in, a typed signed Intent IR come... - [MCL Compiler Pipeline](https://docs.matrixmcl.com/reference/mcl/compiler-pipeline.md): The MCL compiler turns intent.draft (natural language + optional slot pre-fills) into intent.compiled (a typed, signed, deterministically-hashed Intent IR). It does this in 6 di... - [Intent IR](https://docs.matrixmcl.com/reference/mcl/intent-ir.md): Package matrix/mcl/ir defines the Go types for the Intent IR — the central typed artifact that Matrix produces and operates on. Everything the MCL compiler produces ends up here... - [Envelope & Wire Protocol](https://docs.matrixmcl.com/reference/mcl/envelope.md): Package matrix/mcl/envelope is the canonical wire codec for all 15 MCL message kinds. Every message Matrix sends or receives rides inside an Envelope: a typed header, an opaque... - [MatrixScript Language Reference](https://docs.matrixmcl.com/reference/mcl/matrixscript.md): MatrixScript (.mtx) is the declarative language in which MCL is written. Compiler logic, skill procedures, type schemas, and the pipeline wiring all live in .mtx files. The Go r... - [Writing a SKILL.mtx](https://docs.matrixmcl.com/reference/mcl/skill-authoring.md): A skill is the unit of compile-time knowledge in MCL. It tells the compiler what kind of NL requests it handles, what it needs to know, how to extract a typed Frame from them, a... - [mclc CLI Reference](https://docs.matrixmcl.com/reference/mcl/mclc-cli.md): mclc is the MatrixScript compiler CLI. It wires together the MCL runtime packages and provides commands for compilation, validation, hashing, and parsing of .mtx files. - [LLM Client](https://docs.matrixmcl.com/reference/mcl/llm-client.md): Package matrix/mcl/llm implements the interpreter.LLM interface over OpenAI-compatible chat-completion endpoints. It's stdlib-only — no third-party SDK. - [Neo Developer Documentation](https://docs.matrixmcl.com/reference/neo/overview.md): Neo is Matrix's default conversational agent: a recursive LLM tool-calling loop with cortex-backed memory, the shared MCP tool surface, and core_execute delegation to the MCL pi... - [Control Loop](https://docs.matrixmcl.com/reference/neo/control-loop.md): Package matrix/neo/internal/agent implements Neo's recursive LLM tool-calling loop. The conversation transcript IS the state; the model emits text + tool-call intents; the harne... - [Memory System](https://docs.matrixmcl.com/reference/neo/memory-system.md): Package matrix/neo/internal/memory is Neo's memory controller — the 'pager' in the frozen spec's RAM/disk/pager model. The context window is RAM (scarce), cortex is disk (durabl... - [Conversational Recall Lane](https://docs.matrixmcl.com/reference/neo/recall-lane.md): Package matrix/neo/internal/recall is Neo's conversational recall lane: the read-side that surfaces the most RELEVANT past turns of a (now unbounded) conversation thread — reach... - [Conversation Store](https://docs.matrixmcl.com/reference/neo/conversation-store.md): Package matrix/neo/internal/conversation is Neo's durable chat-thread memory. It persists each turn as one JSON file per conversation_id, so history survives reloads, new chats,... - [core_execute Delegation](https://docs.matrixmcl.com/reference/neo/core-execute.md): Package matrix/neo/internal/delegate is the bridge between Neo's conversational loop and the MCL pipeline. It hands a prose intent to the daemon's async HTTP API, services in-wa... - [Write-back Consolidation](https://docs.matrixmcl.com/reference/neo/writeback-consolidation.md): Package matrix/neo/internal/writeback is Neo's automatic background consolidation pass. After each turn, a cheap model sweeps the transcript and promotes durable learnings into... - [Tool Surface](https://docs.matrixmcl.com/reference/neo/tool-surface.md): Package matrix/neo/internal/tools is Neo's tool surface. It reuses the executor's MCP manager + tool registry so Neo's tools are byte-identical to the daemon's (fs, web_search,... - [LLM Client](https://docs.matrixmcl.com/reference/neo/llm-client.md): Package matrix/neo/internal/llm is Neo's OpenAI-compatible function-calling transport. It reuses matrix/mcl/llm's Config, provider detection, and model registry for gateway mete... - [Config System](https://docs.matrixmcl.com/reference/neo/config-system.md): Package matrix/neo/internal/config holds Neo's runtime configuration. The locked operational contract — context-budget thresholds, loop discipline, and the execution surface — c... - [Chronos Developer Documentation](https://docs.matrixmcl.com/reference/chronos/overview.md): Chronos is Matrix's centralized agent scheduler and wake control plane. One always-on chronosd service serves the entire fleet: agents POST alarms (once or cron) with a contextf... - [Architecture](https://docs.matrixmcl.com/reference/chronos/architecture.md): Chronos is a centralized control plane: one chronosd process serves every per-user agent in the Matrix fleet. It is NOT a per-daemon timer — it is the single source of truth for... - [API Reference](https://docs.matrixmcl.com/reference/chronos/api-reference.md): Package chronos/internal/server exposes chronosd over HTTP. All /v1/ endpoints require two-layer auth: the transport bearer on every request, and the agent principal token (X-Ch... - [Auth System](https://docs.matrixmcl.com/reference/chronos/auth-system.md): Package chronos/internal/auth implements Chronos's two-layer principal authentication: a shared transport bearer proves 'a legitimate Matrix daemon,' and an ed25519 agent-DID ch... - [Config System](https://docs.matrixmcl.com/reference/chronos/config-system.md): Package chronos/internal/config loads chronosd configuration from the environment with an optional chronos.config.kvx overlay. Environment variables always win. Mirrors tachyon/... - [Data Model](https://docs.matrixmcl.com/reference/chronos/data-model.md): Package chronos/pkg/types defines the wire contracts and chronos/internal/store implements the Postgres persistence. The alarms table IS the durable timer — state lives in the D... - [Dispatch Worker](https://docs.matrixmcl.com/reference/chronos/dispatch-worker.md): Package chronos/internal/dispatch is the durable poll-and-claim worker that fires due alarms. Single instance now, HA-ready by construction — the DB claim uses FOR UPDATE SKIP L... - [Schedule Engine](https://docs.matrixmcl.com/reference/chronos/schedule-engine.md): Package chronos/internal/schedule computes alarm fire times for the two kinds: once (a relative delay or an absolute instant) and cron (a standard 5-field expression, @descripto... - [Tool Surface](https://docs.matrixmcl.com/reference/chronos/tool-surface.md): Chronos exposes three MCP tools to agents: alarm_set, alarm_list, and alarm_cancel. The MCP stdio proxy (tools/chronos/chronos.mjs) mirrors the tachyon/uwac pattern: initialize/... - [Wake Delivery](https://docs.matrixmcl.com/reference/chronos/wake-delivery.md): Package chronos/internal/wake delivers a due alarm to its agent by asking the router to wake the machine and inject a chat turn. Chronos NEVER talks to Fly or the daemon directl... - [tachyon-tools Developer Docs](https://docs.matrixmcl.com/reference/tachyon/overview.md): 1. Agent-native, not human-native. The CLI is a thin client; the product is the API/MCP/JSON-RPC surfaces. Every response is machine-parseable JSON with stable error codes. 2. S... - [Daemon](https://docs.matrixmcl.com/reference/tachyon/daemon.md): The daemon entry point wires configuration, engine, and transport layers. It supports three modes: HTTP API server, MCP stdio server, and selftest. - [API Server](https://docs.matrixmcl.com/reference/tachyon/api-server.md): The HTTP API server exposes REST endpoints and JSON-RPC on a single listener. It is the primary transport for agent integration when the daemon runs as a service. - [RPC Server](https://docs.matrixmcl.com/reference/tachyon/rpc-server.md): The JSON-RPC dispatcher routes tachyon_ methods to the engine. It is used by both the HTTP API (POST /rpc) and the MCP server (tools/call). - [MCP Server](https://docs.matrixmcl.com/reference/tachyon/mcp-server.md): The MCP (Model Context Protocol) server exposes tachyon verbs as MCP tools over stdio newline-delimited JSON-RPC. This is the primary transport for LLM agent integration when th... - [Compiler](https://docs.matrixmcl.com/reference/tachyon/compiler.md): The compiler wraps forge build and normalizes Foundry's JSON artifact output into a stable, agent-friendly shape. It supports both in-place compiles (the daemon's own project ro... - [Engine](https://docs.matrixmcl.com/reference/tachyon/engine.md): The engine is the single implementation of all tachyon verbs. It is a flat struct that wires together the compiler, tester, simulator, deployer, wallet gate, chain manager, and... - [ABI Encoder](https://docs.matrixmcl.com/reference/tachyon/abi-encoder.md): The ABI encoder bridges JSON-decoded values to the exact Go types required by go-ethereum's ABI packer. JSON decoding produces float64/string/bool/[]interface{}/map[string]inter... - [EVM Client](https://docs.matrixmcl.com/reference/tachyon/evm-client.md): The EVM client wraps go-ethereum RPC operations for chain interaction: tx building, gas estimation, signing, raw broadcast, receipt polling, and debug tracing. It is a thin, sta... - [Deployer](https://docs.matrixmcl.com/reference/tachyon/deployer.md): The deployer plans and executes intent-based contract deployments with idempotency guarantees. It handles both plain contract creation and CREATE2 deterministic deployments, wit... - [Wallet](https://docs.matrixmcl.com/reference/tachyon/wallet.md): The wallet subsystem provides signing backends and a policy gate. Two modes: self-hosted (operator holds the key) and embedded (Paxeer embedded wallet signs server-side via the... - [Registry](https://docs.matrixmcl.com/reference/tachyon/registry.md): The registry is a JSON-file-backed index of compiled artifacts and on-chain deployments. It provides durable, cross-session storage so that a compile today can be referenced by... - [Simulate](https://docs.matrixmcl.com/reference/tachyon/simulate.md): The simulator performs eth_call dry runs without broadcasting. It is a first-class verb in the engine, reflecting the simulation-first design principle: agents dry-run before th... - [Tester](https://docs.matrixmcl.com/reference/tachyon/tester.md): The tester wraps forge test and parses the JSON output into a structured, agent-friendly format. It supports both in-place test runs and self-contained source uploads (same ephe... - [Chains](https://docs.matrixmcl.com/reference/tachyon/chains.md): The chain manager loads preset chain profiles from a JSON file and maintains a map of custom chains registered at runtime. It resolves chain references by profile ID, numeric ch... - [Config](https://docs.matrixmcl.com/reference/tachyon/config.md): The config system loads daemon settings from a .kvx file with environment variable precedence. It supports two wallet modes, capability policy profiles, and custom chain registr... - [Types](https://docs.matrixmcl.com/reference/tachyon/types.md): The pkg/types package defines the shared request/response types used by all transport layers (REST, JSON-RPC, MCP). It is the API contract between the engine and the outside world. - [Financial Workflows Service Entrypoints, API Server, Docs, and Schema Migrations](https://docs.matrixmcl.com/reference/deus/service-entrypoints-api-server-docs-and-schema-migrations.md): This section covers the Deus service shell: the daemon entrypoint, operator CLI, HTTP server assembly, developer sign-in flow, channel and settlement handlers, the repository do... - [Financial Workflows - Discovery extraction, embedding, and index construction](https://docs.matrixmcl.com/reference/deus/discovery-extraction-embedding-and-index-construction.md): This section covers the discovery path that turns a query and a manifest into ranked service results. The pipeline starts by extracting structured constraints from free text, th... - [Financial Workflows - Receipts, vouchers, metering, channels, and storage](https://docs.matrixmcl.com/reference/deus/receipts-vouchers-metering-channels-and-storage.md): This slice of matrix-core turns payment and settlement into a set of tightly linked primitives: EIP-712 signing for quotes, receipts, and vouchers; deterministic hashing for rec... - [Financial Workflows](https://docs.matrixmcl.com/reference/deus/chain-access-auth-wallet-clients-registries-and-manifests.md): This layer connects the authenticated caller identity, the wallet rail, the on-chain service registry, and the manifest schema that describes each listing. It is the part of Deu... - [Financial Workflows - Hosting backends and budget controls](https://docs.matrixmcl.com/reference/deus/hosting-backends-and-budget-controls.md): This section covers the hosted-execution path used to provision, update, and remove Appwrite-backed function deployments, plus the budget gate that decides whether a new hosted... - [Financial Workflows](https://docs.matrixmcl.com/reference/deus/solidity-contracts-deployment-scripts-and-end-to-end-protocol-tests.md): This section covers the on-chain pieces that govern Deus service listings, per-caller escrow windows, and settlement anchoring, together with the Foundry deployment path and the... - [LayerX daemon, auth, chain, accumulator, store, ledger, and types](https://docs.matrixmcl.com/reference/layerx/layerx-daemon-auth-chain-accumulator-store-ledger-and-types.md): LayerX is the always-on settlement fabric for Matrix agents. The daemon gives each agent a DID-scoped account, mints and tracks a USD-denominated balance called USDX, produces a... - [LayerX SettlementAnchor, IERC20, EIP712, SafeERC20, and Deployment Contracts](https://docs.matrixmcl.com/reference/layerx/settlementanchor-ierc20-eip712-safeerc20-and-deployment-contracts.md): The repository documentation states that production src/ has zero external imports, and that safety primitives are reimplemented in-house under src/lib. That makes this section... - [LayerX Forge Std Integration, Fixtures, and Solidity Test Support](https://docs.matrixmcl.com/reference/layerx/forge-std-integration-fixtures-and-solidity-test-support.md): This section captures the vendored Forge Standard Library surface that LayerX uses to write Solidity tests, plus the local test doubles and fixture files that exercise token beh... - [Skills, Agent Packs, and Knowledge Assets](https://docs.matrixmcl.com/reference/skills/agent-engineering-api-design-architecture-and-evaluation-skills.md): This section collects the agent-facing skill packs that teach matrix-core how to reason about accessibility, agent evaluation, API design, architecture, autonomous operation, an... - [Skills, Agent Packs, and Knowledge Assets](https://docs.matrixmcl.com/reference/skills/planning-review-qa-code-quality-cli-and-performance-skills.md): This section documents the skill packs and reference assets that shape planning, review, QA discussion, code quality, CLI design, and performance guidance in paxlabs-inc/matrix-... - [Skills, Agent Packs, and Knowledge Assets](https://docs.matrixmcl.com/reference/skills/react-design-design-system-styling-and-technical-writing-skills.md): This section documents the skill packs that shape React performance guidance, visual design workflows, token-driven UI systems, accessible styling, long-form writing, and docume... - [Skills, Agent Packs, and Knowledge Assets](https://docs.matrixmcl.com/reference/skills/brand-self-improvement-continuous-learning-commit-writing-and-coding-patterns-skills.md): This section groups the repository’s skill packs and companion knowledge assets that shape how Matrix writes brand content, evolves its own behavior, manages learning from sessi... - [Skills, Agent Packs, and Knowledge Assets](https://docs.matrixmcl.com/reference/skills/ck-command-tooling-agent-manifests-and-index-building-assets.md): This section covers the reusable assets that shape Matrix agent behavior and project memory: the ck Context Keeper skill, the agent manifest packs, the continuous-learning obser... - [Coding Standards, Security, and Contributor Policy](https://docs.matrixmcl.com/reference/standards/contribution-workflow-code-review-changelog-and-licenses.md): This part of the repository defines how changes are proposed, reviewed, versioned, and licensed. It combines workflow rules, review gates, change-log conventions, a community co... - [Testing Rules and Project QA Guidance](https://docs.matrixmcl.com/reference/standards/testing-rules-and-project-specific-qa-guidance.md): This section collects the repository’s formal testing expectations and the project-specific QA guidance that contributors are expected to follow. The baseline policy comes from... - [Coding Standards, Security, and Contributor Policy - Patterns, architecture heuristics, and performance guidance](https://docs.matrixmcl.com/reference/standards/patterns-architecture-heuristics-and-performance-guidance.md): This slice of the repository is policy material, not runtime product logic. The documents in rules/ define reusable implementation heuristics for choosing proven starting points... - [Coding Standards, Security, and Contributor Policy: Hook and Lifecycle Conventions](https://docs.matrixmcl.com/reference/standards/hook-and-lifecycle-conventions-across-language-rule-sets.md): This section documents the hook rules that shape contributor workflow across the repository’s language-specific rule sets. The shared baseline defines when hooks run, how much a... - [Coding Standards, Security, and Contributor Policy](https://docs.matrixmcl.com/reference/standards/security-policies-language-specific-security-rules-and-disclosure-endpoints.md): This section documents the project’s security disclosure surface and the source-backed security rule sets that apply across languages. The repository splits policy into a centra... ## FAQ - [General FAQ](https://docs.matrixmcl.com/faq/general.md): High-level questions about Matrix — what it is, the two rails, how it relates to Paxeer, and why it uses typed intents. - [Users FAQ](https://docs.matrixmcl.com/faq/users.md): Everyday questions for people using Matrix — clarifying questions, corrections, memory, long conversations, and reviewing what the agent will do. - [Developers FAQ](https://docs.matrixmcl.com/faq/developers.md): Questions for people building on Matrix — modules, skill authoring, the replay invariant, closed vocabularies, and contribution rules. - [Operations FAQ](https://docs.matrixmcl.com/faq/ops.md): Deployment and operations questions — the per-user topology, the daemon image, waking machines, and idempotency expectations. - [Billing & PAX FAQ](https://docs.matrixmcl.com/faq/billing-pax.md): Questions about how Matrix prices usage — PAX, the rate card, the free tier, bring-your-own-key, receipts, and agent balances. - [Security FAQ](https://docs.matrixmcl.com/faq/security.md): Security questions — credential handling, spend caps on chain, auditability, signed envelopes, and how to report a vulnerability.