stateless
No lore recorded.
- #712swamp repo upgrade should check git status and commit (or surface) the files it changesfeature
- #600Local source-loading should discover a report co-located with its model in a paths.base:manifest extensionfeature
- #591Option to change email in your Swamp Club profile or delete accountfeature
- #572Quality rubric: scope "No slow types" for model extensions (consumed via model+CEL, not type imports)feature
- #510copy method reports success when scp exits non-zero (e.g. 255)bug
Proxmox
Transport-neutral Proxmox VE lifecycle — QEMU VMs (clone, cloud-init config, resize disk, start, stop, delete, in-guest exec) and LXC containers (create-from-template, config, resize, start, stop, delete) — over the REST API directly (token auth) or by running pvesh on the node over SSH (node-local API, reuses an existing jump). Idempotent create/clone/delete + a reachability pre-flight check. Plus host/guest telemetry — a nodeStatus method (CPU load, memory pressure, root-fs fill, disk SMART) and per-guest metrics — read by the @stateless/proxmox-fleet report.
Table Report
A generic data-table report for any swamp model — render materialised resource data as markdown tables, dataview-style, instead of hand-writing a bespoke report per model. Declare a `tableViews` tag (JSON: a list of {spec, columns, where, sort, limit}) for curated views — the config lives in the model's free-form `tags`, so it works on ANY model type with no schema change — or get an auto-table per resource spec with zero config. Column paths are content-relative (e.g. `facets.pricing.perTBMonth`); filters are scalar- equality. Point it at any model, get tables, no TypeScript.
Sourced Kb
A domain-neutral, sourced, versioned knowledge base — the provenance-aware core generalised out of @stateless/llm-catalog. One uniform `entry` record (open `kind` + open `facets` + `claims` + `relations`, like @stateless/inventory), but with a provenance envelope (asOf, source, versionPins, supersededBy) on every volatile assertion, so it can hold external, decaying, contested knowledge honestly — a value without a date + source is not trustworthy here. Declarative lifecycle: `apply` materialises the declared entries (re-run = versioned trend), `update` folds in a public catalog without clobbering local truth, `prune` soft-retires undeclared entries, `contribute` sanitises selected entries into PR-ready public fragments. It knows no domain (no typed facets, no compute methods); a consuming catalog — LLM-ops, cloud-storage pricing — is an instance whose entries carry that domain's kinds and facets.
Review
Human-in-the-loop review canvas — serve a local web form the human gates while the agent keeps working. list mode renders a long candidate list as a curation grid (configurable option-scale + per-item comment) for migrations, triage, and cleanup approvals; doc mode is a pastebin-style markdown editor (editor left, live preview right, optional approve/revise/reject verdict) for reviewing generated docs and gating publishes. Detached serve / status / collect / stop lifecycle; every save dual-writes JSON + markdown + a timestamped append-log, and collect records the result into the data model for workflow consumption. Python-stdlib server bundled; private networks only (URL-token guarded).
Inventory
A neutral, extensible fleet inventory record — the foundational "what exists and its declared attributes" model. Uniform core (id, purpose, components, relations) across atomic and composite items, with an open facet seam (access, power, network, config, management, firmware, interfaces, + custom) so new dimensions layer on without schema changes. Declarative: `apply` materialises one CEL-queryable `device` resource per id; `prune` soft-retires undeclared devices (status change, not deletion — version history preserves the lifecycle trend). Consumer abstractions (telemetry, management, config-drift) depend on it; it depends on nothing.