Repository navigation
Tags
Tags
Costs: a filtered summary reads only the filtered visits' records (#79) The totals, unpriced and billing CTEs aggregated every record the floor holds before the filter applied, so the cost of one run took seconds and grew with the floor's history. The filter now picks the visits first (scoped) and the record CTEs read only those visits by primary key.
perf(metrics): one pass per histogram, and a scrape waits for the one… … already running (#77) Each /metrics scrape joined every event, run and visit ever recorded to every bucket bound, and took over 90 s on the shared Postgres; with a scrape every 15 s on two replicas, six piled up and slowed every floor read. A histogram now buckets each row once with width_bucket, and a scrape that arrives while one is answered shares its answer.
Push agent definitions to every cluster and report which clusters hol… …d the latest version (#64) * Clusters register, and a new agent definition version is queued to each of them A cluster-agent registers at PUT /clusters/{id}. A new latest agent definition writes one agent_definition.changed event per cluster, tagged cluster:<id>, in the put's transaction; a cluster that registers later gets one for every agent it lacks. What a cluster reads back from its kube arrives as agent_definition.reported: a body the floor never stored is adopted as the newest version. GET /agent-definitions/presence answers all, some or none per agent; /{id}/clusters what each cluster holds; /{id}/recipes the settings each variant is briefed with. * Cluster-agent pushes agent definitions ahead of visits and reports what kube holds The cluster-agent registers under FLOOR_CLUSTER_ID every minute and claims its own agent_definition.changed events by cluster:<id>. It applies the latest version's recipes (base and each variant, named as a visit of the same settings would), acks only once kube reads that version back, and posts agent_definition.reported. A watch on the pushed recipes reports hand edits, which the floor adopts. The sweep keeps the newest pushed recipe of each definition and variant. The chart gains clusterAgent.clusterId and watch/patch on the recipe kinds; the client gains agentDefinitions.presence/clusters/recipes and clusters.register.
A release publishes the chart, and the docs install and use one (#49) Installing a floor meant a checkout: the chart lived only in the repository, and the tutorial ran the pipeline tool from a locally built dist. Now publish.yml packages the chart at the release's version and pushes it to oci://ghcr.io/re-cinq/charts/floor, with appVersion as the image tag it runs, so an install of a release names its version once. A checkout carries no appVersion and still requires `version`. docs/install.md installs, upgrades and uninstalls a release; docs/using.md is the CLI, the client, the station SDK and the HTTP API from the published packages. The tutorial installs from the published chart and runs the CLI from npm. The chart README no longer tells the operator to label the namespace, which nothing reads, nor that the subsystem images are private, which they are not. Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
Group costs by billing_mode, read from the agent's init line (#45) Claude Code's stream-json init line says which credential it found (apiKeySource: "none" is the subscription token, anything else a key). The sink already keeps that line as a turn record, so GET /costs can now group by billing_mode: api_key, subscription, or unknown where the transcript says nothing of it (Gemini). The client's CostsGroupBy carries the new group. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
A reworded description reaches the version it belongs to (#43) The definition hash leaves descriptions out, so a put that only adds or rewords one matched the stored version and the floor kept the old body: lore's 66 new station descriptions were all dropped this way. A put now refreshes the stored body of the same version when its prose differs, still without making a new version or reporting one created. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
A station may carry a description of what it does (#42) The floor's station schema stripped unknown keys, so a description a pipeline file wrote never reached anyone who reads the line. It is now an optional field the floor keeps and acts on nothing in; a pipeline file writes it right after the station's kind. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
PreviousNext