Skip to content

v0.4.0 — Authoritative command pipeline

Choose a tag to compare

@MichalPlanetaDev MichalPlanetaDev released this 04 Jul 14:10
· 48 commits to main since this release
5ac336f

v0.4.0 — Authoritative command pipeline

Tickline v0.4.0 introduces the authoritative boundary between typed,
untrusted command claims and deterministic simulation state.

Added

Command validation

  • versioned command envelopes;
  • explicit client and session identity;
  • monotonic session sequences;
  • bounded future-tick validation;
  • velocity bounds;
  • stable numeric rejection codes.

Replay protection

  • duplicate-sequence detection;
  • sequence-regression detection;
  • independent per-session sequence state;
  • commit only after authoritative world acceptance.

Authoritative submission

  • deterministic command translation;
  • authoritative world-level validation;
  • transactional session commit;
  • no session-sequence consumption on rejection;
  • deterministic pending-command ordering.

Evidence integrity

  • evidence for accepted and rejected submissions;
  • fixed-size canonical evidence encoding;
  • SHA-256-linked evidence records;
  • standard SHA-256 test vectors;
  • explicit separation between deterministic world fingerprints and
    cryptographic evidence digests.

Binary evidence archives

  • versioned TLCA archive format;
  • strict fixed-length decoding;
  • truncation and trailing-data detection;
  • record invariant validation;
  • external trusted-head verification;
  • filesystem round-trip coverage.

Forensic replay

  • replay from trusted initial world and session state;
  • observed-tick reconstruction;
  • replay work limits;
  • world, session, and queue-state comparison;
  • regenerated evidence comparison;
  • semantic tampering detection.

Verification

The release is verified with:

bash scripts/check-local.sh

The repository gate covers documentation, C++ builds and tests, sanitizers,
Python tests, Go tests and vet, developer-console version verification, and
Docker checks.

Limitations

This release does not include network transport, byte-level protocol parsing,
transport authentication, encryption, digital signatures, key management,
durable append-only evidence storage, database ingestion, Unity visualization,
or collision and hit validation.

The SHA-256 chain detects modification relative to an independently trusted
head. It does not authenticate the producer of the archive.