Skip to content

v0.5.16

Choose a tag to compare

@CADmind-dev CADmind-dev released this 08 Nov 03:38
· 32 commits to main since this release

Added

  • The operator can lift a wrong disable. POST /v1/operator/unblock {hotkey, reason, readmit?} and
    cadmind-einstein-operator unblock HOTKEY --reason WHY [--readmit]: the block ends, the last strike is taken back
    (the next block is the shorter one again), and the abuse counts the hotkey has so far are marked acted on, so the
    same counts do not disable it again on the next tick. readmit gives back the admission only to a hotkey that had
    passed its entry test and is still approved; otherwise it takes the test again. It never grants a key: the miner
    mints a new one through its usual key request. Logged and kept in the validator's state. Before, a false disable
    could only be undone by editing the state with the validator stopped.

Changed

  • Reference miner: fit first. The prompt and docs/MINER.md now ask a builder to walk only the client's own
    use of the device, to source a fit-critical size from a reference model and then the client's measure before a
    drawing, to price each question's options in numbers, to test a whole feature rather than one point of it, to keep
    covered controls workable, to grip a flexible part by a declared interference, and to make the notes state the
    values the model has.

Fixed

  • The copy check no longer compares rounds of one project started from the same files. An attempt now records
    what it started from (the job's seed workspace, a continuation's base, and the design digest each one's export
    states); an output that shares one of those starts is not compared. With the seed's features subtracted, the small
    delta of a round (an assembly) is the same for every builder: a client's next round, started from the same kept
    version as a round that never delivered, was failed as a copy of it and its miner disabled. Different starts are
    compared as before, and copy entries kept before this release (no start recorded) are compared as before.
  • A miner whose key was revoked while it was down mints a new one at startup. The agent key loaded from state
    is checked with the platform first; one it no longer takes (401) is minted again at once, where before the miner
    waited up to an hour for its idle check. When the platform cannot tell, the stored key is kept.