mesh-issues keeps each design's milestone in the state milestones (history 5), says milestone-set and milestone-moved, and serves milestones, milestone-set and milestone-move. An issue's milestone is its own link of kind milestone, so at most one milestone per issue is checked inside the issue's own write; kind commit links a fixing commit. The triage links no milestone, pull request or commit. import with milestones=N seeds a design's table once. mesh-knowledge's progress reads issue-tracker.milestones and its table parse is gone. Squashed from four commits so the branch history does not carry a compiled bundle that was committed by mistake (6 MB); the path is now in .gitignore.
418 lines
15 KiB
JSON
418 lines
15 KiB
JSON
{
|
|
"milestones": [
|
|
{
|
|
"design": 47,
|
|
"id": "1",
|
|
"issues": [
|
|
973,
|
|
525
|
|
],
|
|
"order": 1,
|
|
"outcome": "A merge during a running delivery is never dropped and needs no person's release; the merge window lives on the bus; a rollout that shares nothing with an open one runs beside it",
|
|
"ref": "47/1",
|
|
"status": "open"
|
|
},
|
|
{
|
|
"design": 47,
|
|
"id": "2",
|
|
"issues": [
|
|
974,
|
|
975,
|
|
976
|
|
],
|
|
"order": 2,
|
|
"outcome": "A ready mark is acted on within seconds, and each pull request has at most one waiting check",
|
|
"ref": "47/2",
|
|
"status": "open"
|
|
},
|
|
{
|
|
"design": 47,
|
|
"id": "2b",
|
|
"issues": [
|
|
1025,
|
|
1019
|
|
],
|
|
"order": 3,
|
|
"outcome": "build-agent and route-proxy live whole in mesh-controller (ADR 0420, accepted 2026-10-17): the controller accepts a reviewed move, mesh-delivery announces each merge with its Approve, and the two modules move; built as two releases before the rule that a milestone is one release",
|
|
"ref": "47/2b",
|
|
"status": "open"
|
|
},
|
|
{
|
|
"design": 47,
|
|
"id": "3",
|
|
"issues": [
|
|
977,
|
|
978,
|
|
1022,
|
|
895,
|
|
1046,
|
|
605,
|
|
1021
|
|
],
|
|
"order": 4,
|
|
"outcome": "A feature with a new seat verb across the controller and the catalogue is one group, one batch, one delivery plan and one Approve: no order lines, no ready mark, each module built and sent once",
|
|
"ref": "47/3",
|
|
"status": "open"
|
|
},
|
|
{
|
|
"design": 47,
|
|
"id": "4",
|
|
"issues": [
|
|
980,
|
|
1065,
|
|
1066,
|
|
1067,
|
|
1068
|
|
],
|
|
"order": 5,
|
|
"outcome": "A delivery backs up the data it moves first, and a failed backup holds it and is said",
|
|
"ref": "47/4",
|
|
"status": "open"
|
|
},
|
|
{
|
|
"design": 47,
|
|
"id": "3-fix",
|
|
"issues": [
|
|
1082,
|
|
1049,
|
|
1047,
|
|
1083,
|
|
1079,
|
|
1084
|
|
],
|
|
"order": 6,
|
|
"outcome": "A group approved together merges in one pass and goes out in one delivery plan, also when its members' tests read each other's repositories",
|
|
"ref": "47/3-fix",
|
|
"status": "open"
|
|
},
|
|
{
|
|
"design": 47,
|
|
"id": "5",
|
|
"issues": [
|
|
981
|
|
],
|
|
"order": 7,
|
|
"outcome": "One read of a module on a node names the commit, build and rollout that put it there",
|
|
"ref": "47/5",
|
|
"status": "open"
|
|
},
|
|
{
|
|
"design": 47,
|
|
"id": "5b",
|
|
"issues": [
|
|
1117,
|
|
1124,
|
|
1128
|
|
],
|
|
"order": 8,
|
|
"outcome": "Decided: building and delivering leave the controller for parts that watch and write keys in the repository `mesh-delivery`, landing in six releases (ADR 0429); the forge module makes that repository from its config, protected before any team reaches it (ADR 0428)",
|
|
"ref": "47/5b",
|
|
"status": "open"
|
|
},
|
|
{
|
|
"design": 47,
|
|
"id": "6",
|
|
"issues": [],
|
|
"order": 9,
|
|
"outcome": "Folded into release 4 by ADR 0429 §10 (the fetch over SSH in R4c, the cut-over in R4e): installed toolchains, builders fetching over SSH with their own key, and an SDK change shipping with its users are built in the builder's new home, so the builder is changed once",
|
|
"ref": "47/6",
|
|
"status": "open"
|
|
},
|
|
{
|
|
"design": 47,
|
|
"id": "R1a",
|
|
"issues": [
|
|
1131
|
|
],
|
|
"order": 10,
|
|
"outcome": "The node-engine, the controller and the parts can read one layout of the have, presence, pulse and stuck keys: mesh-sdk ships it before its users",
|
|
"ref": "47/R1a",
|
|
"status": "open"
|
|
},
|
|
{
|
|
"design": 47,
|
|
"id": "R1b",
|
|
"issues": [
|
|
1132,
|
|
1142,
|
|
1136,
|
|
1145,
|
|
1146,
|
|
1147,
|
|
1160,
|
|
1162
|
|
],
|
|
"order": 11,
|
|
"outcome": "Every node writes what it runs of each module, on its own keys and nobody else's, and the bus says to one part when a connection opens and closes",
|
|
"ref": "47/R1b",
|
|
"status": "open"
|
|
},
|
|
{
|
|
"design": 47,
|
|
"id": "R1c",
|
|
"issues": [
|
|
1134,
|
|
1137
|
|
],
|
|
"order": 12,
|
|
"outcome": "The operator sees every module on every node, with its build, phase and health, in `mesh-delivery-cli` (aliased `nox-delivery`) and its web view",
|
|
"ref": "47/R1c",
|
|
"status": "open"
|
|
},
|
|
{
|
|
"design": 47,
|
|
"id": "R2a",
|
|
"issues": [
|
|
1153
|
|
],
|
|
"order": 13,
|
|
"outcome": "The watchman and the controller can read one layout of the stuck keys: mesh-sdk ships it before its users",
|
|
"ref": "47/R2a",
|
|
"status": "open"
|
|
},
|
|
{
|
|
"design": 47,
|
|
"id": "R2b",
|
|
"issues": [
|
|
1135,
|
|
1154,
|
|
1155,
|
|
1156,
|
|
1157,
|
|
1159
|
|
],
|
|
"order": 14,
|
|
"outcome": "A part, node or check that stops moving is raised as a condition within two minutes, with no timer in a part",
|
|
"ref": "47/R2b",
|
|
"status": "open"
|
|
},
|
|
{
|
|
"design": 47,
|
|
"id": "R2c",
|
|
"issues": [
|
|
1183
|
|
],
|
|
"order": 15,
|
|
"outcome": "The controller says when it last heard each machine from presence alone, and no longer hears the alive message",
|
|
"ref": "47/R2c",
|
|
"status": "open"
|
|
},
|
|
{
|
|
"design": 47,
|
|
"id": "R2d",
|
|
"issues": [
|
|
1158
|
|
],
|
|
"order": 16,
|
|
"outcome": "The node-engine sends no alive message",
|
|
"ref": "47/R2d",
|
|
"status": "open"
|
|
},
|
|
{
|
|
"design": 47,
|
|
"id": "R3a",
|
|
"issues": [
|
|
1200,
|
|
1201,
|
|
1202,
|
|
1203,
|
|
1204,
|
|
1208
|
|
],
|
|
"order": 17,
|
|
"outcome": "The gate, the bridge, the indexer and the teller can read one layout of the source revision, candidates, modules, merges, asks, answers, owed acts, forge messages and conditions, and one function computes the source fingerprint: mesh-sdk ships them before their users (ADR 0437)",
|
|
"ref": "47/R3a",
|
|
"status": "open"
|
|
},
|
|
{
|
|
"design": 47,
|
|
"id": "R3b",
|
|
"issues": [
|
|
1210,
|
|
1211,
|
|
1212,
|
|
1213,
|
|
1214,
|
|
1215,
|
|
1216,
|
|
1217,
|
|
1218
|
|
],
|
|
"order": 18,
|
|
"outcome": "The controller finds the delivery seat's holder by its claim and records each build's fingerprint inputs; the router takes conditions on their one subject; the operator sees no change (ADR 0437)",
|
|
"ref": "47/R3b",
|
|
"status": "open"
|
|
},
|
|
{
|
|
"design": 47,
|
|
"id": "R3c",
|
|
"issues": [
|
|
1235,
|
|
1236,
|
|
1237,
|
|
1238,
|
|
1239,
|
|
1240,
|
|
1241,
|
|
1234,
|
|
1223,
|
|
1233,
|
|
1242
|
|
],
|
|
"order": 19,
|
|
"outcome": "The forge bridge, the indexer and the teller run beside today's mesh-delivery and write their keys; the view shows modules against the controller's source fingerprints; nothing is merged by them yet (ADR 0437)",
|
|
"ref": "47/R3c",
|
|
"status": "open"
|
|
},
|
|
{
|
|
"design": 47,
|
|
"id": "R3d",
|
|
"issues": [
|
|
1321,
|
|
1322,
|
|
1323,
|
|
1324,
|
|
1325,
|
|
1326,
|
|
1317,
|
|
1314,
|
|
1315,
|
|
1316
|
|
],
|
|
"order": 20,
|
|
"outcome": "The gate's keys can carry what the forge needs and the controller answers a what-if as data, so the gate has what it reads before it runs; a failed delivery plan asks the operator Retry on the phone, and a seat whose holder is assigned nowhere passes to its only claimant; the operator sees only the Retry notice (ADR 0450, ADR 0449)",
|
|
"ref": "47/R3d",
|
|
"status": "open"
|
|
},
|
|
{
|
|
"design": 47,
|
|
"id": "R3e",
|
|
"issues": [],
|
|
"order": 21,
|
|
"outcome": "A group reaches the mesh as one source revision written by the gate; the merge's Approve is asked by the teller and answered on the phone until issue 953; the view shows the open asks; today's module mesh-delivery is carried over into the gate when it first holds the seat and ends; no step needs the operator's terminal (ADR 0437, ADR 0450)",
|
|
"ref": "47/R3e",
|
|
"status": "open"
|
|
},
|
|
{
|
|
"design": 47,
|
|
"id": "R4a",
|
|
"issues": [
|
|
1353,
|
|
1354,
|
|
1355,
|
|
1356,
|
|
1357,
|
|
1358,
|
|
1359,
|
|
1360,
|
|
1361,
|
|
1362,
|
|
1363,
|
|
1364,
|
|
1298,
|
|
1308
|
|
],
|
|
"order": 22,
|
|
"outcome": "The shared layouts of release 4 are on mesh-sdk's main before their users pin them: the catalogue, the validator and the composition over a plain input, the fingerprint's new form, and the key layouts of the builder, the checker, the kept verdicts, the manifests and the candidates; the node-engine reports the user namespaces capability (ADR 0453 clauses 1, 2, 3)",
|
|
"ref": "47/R4a",
|
|
"status": "open"
|
|
},
|
|
{
|
|
"design": 47,
|
|
"id": "R4b",
|
|
"issues": [
|
|
1375,
|
|
1337
|
|
],
|
|
"order": 23,
|
|
"outcome": "mesh-controller and the node-engine use the catalogue, the validator and the composition from mesh-sdk and delete their copies; the controller composes every node both ways on the live facts and the two agree before this is delivered; it writes the grants and credential bindings the assigner reads; its unit level meets its bound (ADR 0453 clauses 1, 3)",
|
|
"ref": "47/R4b",
|
|
"status": "open"
|
|
},
|
|
{
|
|
"design": 47,
|
|
"id": "R4c",
|
|
"issues": [
|
|
1309,
|
|
1287,
|
|
1288,
|
|
1289,
|
|
1290,
|
|
1291,
|
|
1292,
|
|
1251,
|
|
1293
|
|
],
|
|
"order": 24,
|
|
"outcome": "The new parts run dark beside today's: the indexer writes the manifests by digest and the fingerprints in the new form beside today's (its own, first delivery), then the build modules (the Go build module, the Node and TypeScript build module: toolchain, sandbox, fetch, digest, test, build), the builder, the checker writing `mesh/check` as a status the forge does not require, and the assigner's composition check writing into the checker's report; the build seat's accounts are decided by a record before the build modules' pull requests are opened (ADR 0453 clauses 4, 6, 7, 8, 11, 12, 16; ADR 0465 §4); the builder is ADR 0478's. It is delivered in ADR 0465 §5's order: mesh-sdk's layouts; the forge bridge and the indexer with the controller's facts in format 2; the build modules; the builder; the checker; the bus user list's composer moved into mesh-sdk; the assigner's composition check; the fetch and run steps. The build modules each run as an account of their own with a forge key known read-only on one forge user (ADR 0466); each builds with the node's installed toolchain at the agreed version and does not refuse on a node with another (ADR 0477, issue 1572), answers a long step with its id and finishes it on a key, is called on a named machine, and runs on the four nodes that run the build agent today (ADR 0469)",
|
|
"ref": "47/R4c",
|
|
"status": "open"
|
|
},
|
|
{
|
|
"design": 47,
|
|
"id": "R4d",
|
|
"issues": [],
|
|
"order": 25,
|
|
"outcome": "Four modules stop being built from a Dockerfile: route-proxy, nats, n8n and mail's autoconfiguration module (automx, replaced by a Go program), each rework its own release step, nats in a delivery of its own; free between R4a and R4e and never in the same delivery as another release (ADR 0452, ADR 0453 clauses 13, 14, 16)",
|
|
"ref": "47/R4d",
|
|
"status": "open"
|
|
},
|
|
{
|
|
"design": 47,
|
|
"id": "R4e",
|
|
"issues": [
|
|
1304
|
|
],
|
|
"order": 26,
|
|
"outcome": "The controller asks no build: a build is keyed by its fingerprint, the new form becomes the only one as one group, and a merge builds nothing its check built; builders fetch over SSH, so an SDK change ships with its users; the vendored copies leave mesh-controller and mesh-sdk; delivered only once the builder's artifact digests equal build-agent's (ADR 0453 clauses 2, 4, 5, 6)",
|
|
"ref": "47/R4e",
|
|
"status": "open"
|
|
},
|
|
{
|
|
"design": 47,
|
|
"id": "R4f",
|
|
"issues": [
|
|
709,
|
|
1300,
|
|
1301,
|
|
1302
|
|
],
|
|
"order": 27,
|
|
"outcome": "A pull request carries one required status that says what it proved and how long each part took; the controller's composition check and its replays are deleted with the two old statuses; the controller's deletions R3e makes possible go; each level's times are measured, and a bound fails a repository from the first check that meets it (ADR 0447, ADR 0450 §8, ADR 0453 clauses 4, 9, 10)",
|
|
"ref": "47/R4f",
|
|
"status": "open"
|
|
},
|
|
{
|
|
"design": 47,
|
|
"id": "R4g",
|
|
"issues": [
|
|
1887,
|
|
1295,
|
|
1296,
|
|
1303
|
|
],
|
|
"order": 28,
|
|
"outcome": "The last milestone of release 4 and release 5 as one, with one switch-over and no rehearsal (ADR 0524 §1): builds and checks are asks on streams that each build node pulls when it has a free slot, deliveries first, with nothing holding checks and no controller queue (ADR 0525); the assigner is made with its composition check, writes each node's wants compared with what the controller sends and every difference, and the view answers the asks that need no proof of who answered (ADR 0528, ADR 0437 §10); no module's fingerprint takes the builder (ADR 0530); the scripts of the repositories a module is built from, build-agent with its socket and Dockerfile code, the toolchain images and the controller's build code go, and the builder delivers its own module, the build modules and the controller from its keys (ADR 0453 clauses 5, 8, 10; ADR 0524 §5, §7); the ways to deliver without the builder are recorded (ADR 0526); hq's four checks are Go tests (ADR 0527); each repository's script goes (ADR 0529); the word for the composition check's predecessor is struck. Its pull requests are opened only after five readings, the revert path read, not shown on a test merge (ADR 0524 §3)",
|
|
"ref": "47/R4g",
|
|
"status": "open"
|
|
},
|
|
{
|
|
"design": 47,
|
|
"id": "R6",
|
|
"issues": [
|
|
1942,
|
|
1945,
|
|
1943,
|
|
1944,
|
|
1946,
|
|
1906,
|
|
1130
|
|
],
|
|
"order": 29,
|
|
"outcome": "Each node applies from its wants the compositions its own node agent composes (ADR 0547 §2; as released it applied the controller's signed ones), a new version reaches the module's canary first and the rest once it is healthy there, a move a person must allow is asked before its want, the view says what is moving, settled, stuck and delivered, and the plans are deleted from the code; switched over by release 5's last plan (ADR 0539)",
|
|
"ref": "47/R6",
|
|
"status": "open"
|
|
}
|
|
],
|
|
"said": "generated"
|
|
} |