Repository navigation
Chronos DB 0.4.10
Rules for agents that run on their own. Merge policies gain rules on values, a breaker for a fleet, a guard
against prompt injection, and a reviewer agent that can decide every merge without being able to approve what only a
person should.
The macOS builds need macOS 13 or later, as for 0.2.0. While the build service is offline, this release was
built on the maintainer's Mac with the release's own toolchain (Rust 1.95.0, zig 0.15.2 for every target) and
signed as before, as the chronos-release service account.
row_rules: conditions on the rows a merge changes, overold.colandnew.col, read as a CHECK
('payments: new.amount >= -50; prices: new.price <= old.price * 1.2'). Reasons name rows by key, never values.max_nulled: most values one merge may empty.all_rows_per_hour,all_deletes_per_hour,all_effects_per_hour: limits on every merge into main by any
agent keeping to a policy, together, a reviewer's approvals included.untrusted_columns,untrusted_guards: a world that may have read text from outside (tickets.body) and
changes a guarded table waits for a person. The policy's worlds keep their reads without holding for stale ones.spot_check: one merge in n, at random, waits for a person.review_every: every merge waits for review, so a reviewer agent decides each one.person_only: the rules whose holds a reviewer agent may not approve (by default deletes, schema, untrusted
reads, the fleet limits and spot checks); an admin's agent can't merge those either.SHOW REVIEWShas a
needs_personcolumn.- Holds notify
chronos_review_held, so a reviewer listens instead of polling. untrusted_columns = '*'andtrusted_columns: every text column untrusted by default, with exceptions.
'tickets.*'takes every text column of one table.- Tainted rows: rows a merge writes after its world read untrusted text are tainted, and reading one counts as
reading untrusted text. Kept in thetalliesfile; a person's own merge or a delete clears a row. - Reasons without values for agents: row keys that are text, what a merge check found and what a SELECT gave show
as…to agents, a reviewer among them, in refusals,SHOW REVIEWS,CHECK READSandcheck_merge_policy.
People see them as they are. watch_totals,max_shift: scalar queries run before and after a merge; one that moves more thanmax_shift
percent (10 by default) holds it, for a person by default.max_unusual: a merge far bigger than the policy's usual (the median of its last 50) waits: drift.canary,canary_wait: a big merge lands a few rows first (55000), the rest after the wait.effects_delay: effects an agent's merge lands aredelayed: no claim, noNOTIFY, andUNDO MERGE
meanwhile takes them back unsent.- A run's own
row_rules:CREATE WORLD ... WITH (row_rules = '...')adds conditions on top of the policy's. - Changed: another agent with no policy can't merge a world held for person-only rules, but the world's own agent
whose policy an admin removed still can.
Every change in detail: https://github.com/Abhishekxdg/chronosdb/blob/main/CHANGELOG.md