8000 GitHub - tavakyan/timeless: The Timeless Systems Manifesto · GitHub
[go: up one dir, main page]

Skip to content
tavakyanPublic

About

The Timeless Systems Manifesto

Resources

Stars

1 star

Watchers

1 watching

Forks

8000

Latest commit

 

History

7 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 

Repository files navigation

Software That Keeps Its Promises

The Timeless Manifesto. The engineering handbook it was distilled from is preserved in HANDBOOK.md.

Engineering is the discipline of making reality simpler without making it false.

Software is a promise made executable. A lasting system keeps that promise as reality changes. Code, architecture, process, velocity, and automation are means. The observed outcome is the proof.

1. Name the promise

State who receives what result, under which conditions, within which limits, at what cost, and what must never happen.

Separate observation, inference, and assumption. Give every critical invariant a falsifier.

Tell: The team can demonstrate what it built but cannot demonstrate what changed for the user.

2. Prove the whole path

Build the smallest complete path from real input to user-visible outcome.

A component test proves a component claim. It does not prove integration, recovery, or value. When the path fails, fix the earliest false assumption and rerun the same proof.

Tell: Every subsystem is green, but the promised outcome cannot be produced end to end.

3. Give each truth one authority and each consequence one owner

Every mutable fact has one authority; every other appearance is an explicit copy or derivation.

Draw boundaries around related change, failure, and responsibility. State contracts in the consumer's terms: meaning, timing, failure, and compatibility.

Give each component only the data and authority its promise requires. Separate proposing, approving, and performing consequential actions.

Tell: Two places can disagree about the same fact, or one change requires unrelated owners to move together.

4. Design for time

Assume work will be duplicated, delayed, reordered, interrupted, and retried.

Make effects idempotent or reconcilable. Make migrations preserve meaning and state; make rollbacks restore them. Keep enough history to explain and repair important outcomes, and delete it when its purpose ends.

Tell: The design works only on a fresh database, in one uninterrupted run, or when nobody retries.

5. Make complexity earn its place - and preserve the exit

Every abstraction, dependency, queue, option, and exception must remove more present complexity, risk, or toil than it introduces.

Measure before accommodating. Prefer reversible decisions, replaceable parts, exportable state, bounded dependencies, and an explicit migration path. Every replacement ends with deletion of the superseded path.

Tell: The strongest argument for a layer is "we may need it later," or removing it would change no current promise.

6. Require a witness

Instrument the promise: which outcome failed, for whom, where, and why.

Measure cost per useful result, not consumption alone. A change is not accepted on its author's account. Verification must read the actual facts, exercise realistic failure and recovery, and stand apart from the work that produced it.

Production is cheap. Trustworthy verification is scarce.

Tell: Dashboards remain green while users fail, or the author - human or machine - is the only evidence that the work succeeded.

The working loop

For every meaningful change:

  1. State the promise and its limits.
  2. Name the riskiest assumption and what would disprove it.
  3. Build the smallest complete path.
  4. Exercise interruption, retry, failure, and recovery.
  5. Verify the outcome independently under realistic conditions.
  6. Keep only what earned its place.

A system lasts not by predicting every future. It lasts by telling the truth about the present, making one complete move, preserving what others now depend on, and remaining able to change again.

About

The Timeless Systems Manifesto

Resources

Stars

1 star

Watchers

1 watching

Forks

Releases

Packages

Contributors

0