Living document · Version 0.2 ·
SyncThinkDesign
A proposal about how systems evolve when the processes that conceive, build and improve them stop waiting for one another and start influencing each other continuously.
- SyncThinkDesign
A proposal by Iván Braida about the evolution of systems. It holds that Capture (Sync), Ideate (Think), Execute (Design) and Optimize (Refine) can operate in parallel and influence one another while a system is conceived, built and used, so that its evolution is not fully determined from the start. Abbreviated STD.
Read the foundations- AAA3
AI-Addressable Application — Three-Plane Architecture, also written AAA³. An application architecture proposed by Iván Braida and developed at Braidata: a human plane (the interface), a declarative plane (a canonical JSON document) and an execution plane (engine and APIs) operate on the same project, so that a person, a script or an external AI can create and modify it without the application depending on a built-in model. It brings some STD principles into executable systems; it does not define the method.
See the architecture
- CaptureSync↓ Ideate: data and context
↑ Ideate: what to observe - IdeateThink↓ Execute: ideas and decisions
↑ Execute: findings - ExecuteDesign↓ Optimize: the system in use
↑ Optimize: improvements - OptimizeRefine↓ Capture: new questions
↑ Capture: signals - Evolving system
Three levels
The site keeps the proposal apart from the tools that instrument it and from the technologies that implement it. Each level rests on the one above, and what is learned in the lower levels can come back to question the upper ones.
- AFoundations
The original proposal: its principles, its scope and its view of how systems evolve. This is what defines SyncThinkDesign.
- BFormalization
An operational interpretation in progress: mechanisms, hypotheses, measures and protocols for applying and evaluating the foundations where they are relevant.
- CAAA3
A three-plane application architecture —human, declarative and execution— that brings some principles into executable systems and returns observations and questions to the method.
State of knowledge
Every claim carries an identifier and a status. Principles express the proposal; mechanisms are tools for instrumenting it; hypotheses await evidence; observations and results come from real experiments. The figures are computed from the published text.
- Principles
- 12
- Mechanisms
- 7
- Hypotheses
- 8
- Implementations
- 7
- Observations
- 3
- Measured results
- 1
- Aspirations
- 5
- Open question
- 6
Contents
- 01Manifesto
The starting statement: what SyncThinkDesign questions, what it proposes and what it does not yet claim.
- 02Foundations
The four processes, synchronization, organic and continuous evolution, and emergence; the scope of the proposal and how it relates to other approaches.
- 03Formalization
Optional mechanisms for instrumenting synchronization, hypotheses about its effects and measures for testing them.
- 04AAA3
AAA³: what it means, its three planes, six invariants, the conformance of our applications and its relation to STD.
- 05Experiments
Records of real tests, with their question, their procedure and what went wrong.
- 06Research
The main line of research and working notes with version, history and references.
- 07Adoption
How to explore STD in technology, organizations, education or creative work, without depending on our tools.
- 08Discussion
How to challenge the proposal, contribute counterexamples or point out prior work we have missed.