Point specification at external journal and implementation plan
Journal content and the implementation plan now live only in development-journal; the project keeps normative docs and the local docs/journal symlink.
This commit is contained in:
parent
6c66e8c0b7
commit
7800e9ddf6
1 changed files with 5 additions and 5 deletions
|
|
@ -2,11 +2,11 @@
|
||||||
|
|
||||||
This document is the normative product specification for Lazaret. It defines the
|
This document is the normative product specification for Lazaret. It defines the
|
||||||
problem, stable vocabulary, architecture, and requirements. The
|
problem, stable vocabulary, architecture, and requirements. The
|
||||||
[TLA+ application protocol model](protocol/Lazaret.tla) defines lifecycle and communication
|
[TLA+ application protocol model](protocol/Lazaret.tla) defines lifecycle and
|
||||||
semantics. The [implementation plan](implementation-plan.md) records current
|
communication semantics. Current implementation strategy, experimental results,
|
||||||
technology choices, configuration schema, sequencing, and validation work.
|
and historical rationale live in the development journal (local checkout:
|
||||||
Experimental results and historical rationale belong in the
|
[journal index](journal/00_INDEX.md), including the
|
||||||
[journal](journal/00_INDEX.md).
|
[implementation plan](journal/implementation-plan.md)).
|
||||||
|
|
||||||
## 1. Problem Statement
|
## 1. Problem Statement
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue