ProbOS — Reconciled AD/BF Ledger¶
Generated file — do not edit by hand.
Regenerate with python scripts/gen_ad_ledger.py (add --online to refresh the
GitHub issue layer). The generator is scripts/gen_ad_ledger.py; the pinned
snapshot is docs/development/ad-ledger-snapshot.json.
This replaces a hand-made 2026-03-31 snapshot that had been stale for months.
Read the ceiling here, not from a tree scan. AD and BF numbers are minted by audits and reviews that file a GitHub issue before any code exists. A recursive scan of the working tree therefore reports a ceiling that is already too low, and reports intentionally-allocated numbers as free. That is how collisions happen.
No number below the ceiling is free merely because this file does not account
for it. Gaps are listed as unaccounted, which means the four authorities are
silent — not that the number may be reused. Refresh the issue layer and check
gh issue list --search "AD-NNNN in:title" --state all before minting.
This file observes the ledger. It does not correct it: nothing is renumbered or retired here, and disagreements between the authorities are reported below rather than resolved.
Ceilings¶
Derived from all four authorities. A tree scan sees only the numbers that reached code, so it reports a lower ceiling than this.
| Series | Highest allocated | Next free | Highest with code | Allocated above the code ceiling |
|---|---|---|---|---|
| AD | AD-1305 | AD-1306 | AD-1305 | (none) |
| BF | BF-873 | BF-874 | BF-873 | (none) |
Where each layer came from¶
| Authority | Availability | Captured | Extent |
|---|---|---|---|
git log commit subjects |
pinned snapshot | 2026-09-05T19:54:05+00:00 at 0dbeebd9 |
2492 subjects, 1001 numbers |
DECISIONS.md, decisions-era-1-genesis.md, decisions-era-2-emergence.md, decisions-era-3-product.md, decisions-era-4-evolution.md, decisions-era-5-unification.md |
live, every run | at check time | AD/BF entry headings |
PROGRESS.md, progress-era-1-genesis.md, progress-era-2-emergence.md, progress-era-3-product.md, progress-era-4-evolution.md, progress-era-5-unification.md |
live, every run | at check time | AD/BF status head lines |
gh issue list --state all |
pinned snapshot (network) | 2026-08-29T05:45:15+00:00 | 1331 issues, 916 numbers |
The two pinned layers are refreshed by running the generator (--online for issues). --check re-renders from the pinned snapshot and a fresh parse of the two live authorities, so it opens no socket and spawns no subprocess.
Lifecycle¶
| State | AD | BF | Meaning |
|---|---|---|---|
allocated-open |
78 | 10 | assigned, issue open, no shipped code |
deferred |
0 | 0 | assigned, explicitly postponed |
superseded |
1 | 0 | replaced by a later number |
retired |
7 | 0 | abandoned, number not reusable |
shipped |
941 | 531 | code in history |
Allocated and open — do not reuse these numbers¶
88 numbers. Every one is assigned. A recursive tree scan reports the ones without code as free.
| Number | Issue | Why | Title |
|---|---|---|---|
AD-1261 |
#1311 | issue #1311 open, no code | AD-1261: the authority domain — an agent cannot see its own ceiling, so it can only refuse, never escalate |
AD-1260 |
#1310 | issue #1310 open, no code | AD-1260: the wellness domain, and the line between first person and third — the Counselor cannot read her own assessment |
AD-1250 |
#1294 | issue #1294 open, no code | AD-1250: a joint allowance/ration search retains 32 rows where the ordered search retains 13 |
AD-1246 |
#1241 | issue #1241 open, no code | AD-1246: a long execution should promote, not be capped at 30 seconds |
AD-1245 |
#1238 | issue #1238 open, no code | AD-1245: a verdict must distinguish judged-and-refused from could-not-judge |
AD-1244 |
#1237 | issue #1237 open, no code | AD-1244: a refusal must say what is missing, and a verdict must not contradict itself |
AD-1243 |
#1236 | issue #1236 open, no code | AD-1243: show the Captain what a reply actually consulted |
AD-1242 |
#1234 | issue #1234 open, no code | AD-1242: the verifier is asked whether claims are supported, and shown no evidence |
AD-1240 |
#1239 | issue #1239 open, no code | AD-1240: offload large tool results to the workspace instead of destroying them |
AD-1236 |
#1205 | issue #1205 open, no code | AD-1236: the install rung means enable a registered MCP server (implements #1172 decision B) |
AD-1229 |
#1202 | issue #1202 open, no code | AD-1229: did the action land - closing the loop between an agent's action and its effect |
AD-1228 |
#1201 | issue #1201 open, no code | AD-1228: a standing interest - an agent is told when ship state changes, instead of polling for it |
AD-1225 |
#1193 | issue #1193 open, no code | AD-1225: an agent pays a full ~18K-token prompt to decide to say nothing |
AD-1216 |
#1175 | issue #1175 open, no code | AD-1216: approve from the chat, not only from the Bridge |
AD-1215 |
#1172 | issue #1172 open, no code | AD-1215: decide whether ProbOS needs its own extension model or should use plugins |
AD-1214 |
#1171 | issue #1171 open, no code | AD-1214: pre-clear a class so routine decisions stop notifying |
AD-1213 |
#1170 | issue #1170 open, no code | AD-1213: the chain of command does not reach the approval path |
AD-1212 |
#1166 | issue #1166 open, no code | AD-1212: action requests cannot be meaningfully approved in the HXI |
AD-1208 |
#1154 | issue #1154 open, no code | AD-1208: bound agentic turns by risk and cost, not by a flat iteration cap |
AD-1207 |
#1152, #1153 | issue #1152, #1153 open, no code | AD-1207: nothing surfaces a fault the ship has found to the Captain |
AD-1206 |
#1151, #1153 | issue #1151, #1153 open, no code | AD-1206: an approved repair brief becomes a GitHub issue (the missing consumer) |
AD-1205 |
#1150, #1153 | issue #1150, #1153 open, no code | AD-1205: fault detection is too narrow to see a defect that breaks everything |
AD-1202 |
#1142 | issue #1142 open, no code | AD-1202: the HXI has no control primitives -- 478 controls styled inline, zero shared components |
AD-1200 |
#1137 | issue #1137 open, no code | AD-1200: hierarchical AGENTS.md discovery for external repositories |
AD-1199 |
#1136 | issue #1136 open, no code | AD-1199: a typed human-claim lifecycle |
AD-1198 |
#1135, #1140 | issue #1135, #1140 open, no code | AD-1198: authenticated transport admission, gated on the existing two-node cluster |
AD-1197 |
#1134, #1140 | issue #1134, #1140 open, no code | AD-1197: sign canonical federation envelopes and add replay protection |
AD-1196 |
#1133, #1140 | issue #1133, #1140 open, no code | AD-1196: bind did:probos identifiers to Ed25519 keys, with rotation and revocation |
AD-1195 |
#1132 | issue #1132 open, no code | AD-1195: an event persistence contract -- decide what events.db can answer |
AD-1194 |
#1131 | issue #1131 open, no code | AD-1194: unify capability triage through AD-854 |
AD-1193 |
#1130 | issue #1130 open, no code | AD-1193: conversational streaming |
AD-1192 |
#1129 | issue #1129 open, no code | AD-1192: a durable plan writer for WorkItem.steps |
AD-1191 |
#1128 | issue #1128 open, no code | AD-1191: typed evidence from a delegated subtask |
AD-1190 |
#1127 | issue #1127 open, no code | AD-1190: aggregate budget across a delegation tree |
AD-1189 |
#1126 | issue #1126 open, no code | AD-1189: deferred tool schemas in swe_harness |
AD-1187 |
#1124, #1139 | issue #1124, #1139 open, no code | AD-1187: a governed agent-facing claim and discovery surface over AD-496 |
AD-1186 |
#1123, #1138 | issue #1123, #1138 open, no code | AD-1186: Ship Trials -- a release catalog and policy over the existing evaluators |
AD-1174 |
#1105 | issue #1105 open, no code | AD-1174: live tool-call progress in the HXI |
AD-1156 |
#1083 | issue #1083 open, no code | AD-1156: Plan/execute mode provider (MAF framing; supersedes the AD-1150 approach) |
AD-1152 |
#1079 | issue #1079 open, no code | AD-1152: Agentic-loop span correlation (OpenTelemetry prerequisite) |
AD-1137 |
#1056 | issue #1056 open, no code | AD-1137: Quickstart + Alpha→Beta getting-started stability (probos doctor) (Phase 35) |
AD-1136 |
#1055 | issue #1055 open, no code | AD-1136: First-class chat channel adapter (finish Discord/Slack gateway) (Phase 24) |
AD-1135 |
#1054 | issue #1054 open, no code | AD-1135: probos setup provider wizard — BYO OpenAI-compatible model (Phase 35) |
AD-1134 |
#1053 | issue #1053 open, no code | AD-1134: PyPI release + lightweight install path (Phase 35) |
AD-703 |
#479 | issue #479 open, no code | AD-703: Starfleet Command — fleet-wide policy distribution across instances |
AD-392 |
— | mentioned by an authority, no code and no closure | |
AD-391 |
— | mentioned by an authority, no code and no closure | |
AD-390 |
— | mentioned by an authority, no code and no closure | |
AD-389 |
— | mentioned by an authority, no code and no closure | |
AD-375 |
— | mentioned by an authority, no code and no closure | |
AD-347 |
— | a tracker head marks it open | |
AD-346 |
— | mentioned by an authority, no code and no closure | |
AD-345 |
— | mentioned by an authority, no code and no closure | |
AD-344 |
— | mentioned by an authority, no code and no closure | |
AD-343 |
— | mentioned by an authority, no code and no closure | |
AD-342 |
— | mentioned by an authority, no code and no closure | |
AD-341 |
— | mentioned by an authority, no code and no closure | |
AD-340 |
— | mentioned by an authority, no code and no closure | |
AD-339 |
— | mentioned by an authority, no code and no closure | |
AD-338 |
— | mentioned by an authority, no code and no closure | |
AD-337 |
— | mentioned by an authority, no code and no closure | |
AD-323 |
— | mentioned by an authority, no code and no closure | |
AD-320 |
— | mentioned by an authority, no code and no closure | |
AD-319 |
— | mentioned by an authority, no code and no closure | |
AD-318 |
— | mentioned by an authority, no code and no closure | |
AD-315 |
— | mentioned by an authority, no code and no closure | |
AD-312 |
— | mentioned by an authority, no code and no closure | |
AD-309 |
— | mentioned by an authority, no code and no closure | |
AD-308 |
— | mentioned by an authority, no code and no closure | |
AD-305 |
— | mentioned by an authority, no code and no closure | |
AD-304 |
— | mentioned by an authority, no code and no closure | |
AD-284 |
— | mentioned by an authority, no code and no closure | |
AD-283 |
— | mentioned by an authority, no code and no closure | |
AD-282 |
— | mentioned by an authority, no code and no closure | |
AD-281 |
— | mentioned by an authority, no code and no closure | |
AD-277 |
— | mentioned by an authority, no code and no closure | |
AD-276 |
— | mentioned by an authority, no code and no closure | |
AD-274 |
— | mentioned by an authority, no code and no closure | |
BF-867 |
— | mentioned by an authority, no code and no closure | |
BF-843 |
#1313 | issue #1313 open, no code | BF-843: BackupService is wired but never invoked — zero SQLite snapshots have ever been taken |
BF-839 |
#1305 | issue #1305 open, no code | BF-839: sandbox scratch cleanup ownership needs a state machine, not flags |
BF-838 |
#1304 | issue #1304 open, no code | BF-838: 22 of 49 declared databases are outside backup coverage, including schema_versions and four grant stores |
BF-818 |
#1282 | issue #1282 open, no code | BF-818: the watch dispatch loop is started, repaired, and has no producer |
BF-809 |
#1273 | issue #1273 open, no code | BF-809: the AD-272 decision cache keys on a per-cycle correlation_id, so it may never hit |
BF-741 |
#1200 | issue #1200 open, no code | BF-741: an agent's own false claim is the top recall hit for the question that produced it |
BF-689 |
#1090 | issue #1090 open, no code | BF-689: an agent misattributes real records it retrieved correctly (read-path attribution confabulation) |
BF-7 |
— | mentioned by an authority, no code and no closure | |
BF-5 |
— | mentioned by an authority, no code and no closure |
Deferred¶
(none)
Superseded¶
| Number | Issue | Why | Title |
|---|---|---|---|
AD-705 |
#481, #523, #554, #555, #556, #557, #558 | a tracker head marks it superseded | AD-705: Voice Stack Backends — Whisper STT, Deepgram STT, Coqui/Piper TTS, Porcupine wake word |
Retired — never reusable¶
| Number | Issue | Why | Title |
|---|---|---|---|
AD-1188 |
#1125, #1139 | issue #1125 closed as not planned, no code | AD-1188: orchestration-mode ablation rig |
AD-1150 |
#1068, #1075, #1083 | issue #1075 closed as not planned, no code | Epic: Agentic harness parity — loop conversation mechanics (AD-1146..AD-1150) |
AD-1149 |
#1074 | issue #1074 closed as not planned, no code | AD-1149: Prompt caching / stable prefix reuse |
AD-842 |
#817, #821 | issue #821 closed as not planned, no code | AD-842: Per-agent tool grants in the ACM profile |
AD-840 |
#815, #819 | issue #819 closed as not planned, no code | AD-840: HXI Skill Registry + per-agent ACM skill-assignment surface |
AD-709 |
#485 | issue #485 closed as not planned, no code | AD-709: MemoryForge — implanted birth memories + curated memory banks (Long Horizon) |
AD-693 |
#387 | issue #387 closed as not planned, no code | AD-693: Federation Knowledge Sync |
Shipped¶
AD (941): 1, 19-139, 142-153, 228, 262-273, 293-300, 302, 311, 313-314, 316-317, 321-322, 324, 348-355, 357-373, 376-388, 393-419, 423-502, 507-530, 532, 534, 538-541, 543, 550-554, 556-558, 560-577, 579-623, 625-680, 682-683, 685-692, 694-702, 704, 706-708, 710-766, 790-813, 815-828, 832-839, 841, 843, 845-847, 853-956, 958-966, 972, 975-1019, 1021-1038, 1040-1055, 1065, 1068-1089, 1091-1095, 1119-1133, 1138-1148, 1151, 1153-1155, 1157-1173, 1175-1185, 1201, 1203-1204, 1209-1211, 1217-1224, 1226-1227, 1230-1235, 1239, 1241, 1247-1248, 1251, 1256-1259, 1265, 1267, 1269-1271, 1273-1285, 1291-1305
BF (531): 4, 6, 8-13, 23-25, 27, 29-37, 39-41, 43-44, 49, 53, 57-60, 63-69, 71, 76, 78-80, 82-86, 99-104, 106, 108-116, 118, 123-175, 177-179, 183-201, 203-204, 206-219, 222-326, 331-332, 597-680, 682-688, 690-740, 742-808, 810-817, 819-837, 840-842, 844-866, 868-869, 871-873
Unaccounted — silent, not free¶
Numbers below the ceiling that no authority mentions. The issue layer is a snapshot and audits allocate before writing code, so silence here is absence of evidence. Confirm against live issues before minting.
AD (278): 2-18, 140-141, 154-227, 229-261, 275, 278-280, 285-292, 301, 303, 306-307, 310, 325-336, 356, 374, 420-422, 503-506, 531, 533, 535-537, 542, 544-549, 555, 559, 578, 624, 681, 684, 767-789, 814, 829-831, 844, 848-852, 957, 967-971, 973-974, 1020, 1039, 1056-1064, 1066-1067, 1090, 1096-1118, 1237-1238, 1249, 1252-1255, 1262-1264, 1266, 1268, 1272, 1286-1290
BF (332): 1-3, 14-22, 26, 28, 38, 42, 45-48, 50-52, 54-56, 61-62, 70, 72-75, 77, 81, 87-98, 105, 107, 117, 119-122, 176, 180-182, 202, 205, 220-221, 327-330, 333-596, 681, 870
Inconsistencies — reported, deliberately not fixed¶
This generator observes the ledger; correcting an append-only history is a separate decision for a human.
A collision below means two issues each lead with the identical number. Sub-allocations that share a base (AD-423a, AD-423b, AD-423c) and epics that name their children in the title are normal and are not counted.
AD-272— code is in history but #1273 is still open.AD-443— collision: 2 issues each lead with this number: #42, #433.AD-473— collision: 2 issues each lead with this number: #67, #435.AD-474— collision: 2 issues each lead with this number: #68, #436.AD-482— collision: 2 issues each lead with this number: #76, #434.AD-496— code is in history but #1124 is still open.AD-529— collision: 2 issues each lead with this number: #103, #437.AD-538b— collision: 2 issues each lead with this number: #26, #418.AD-539c— collision: 2 issues each lead with this number: #106, #454.AD-539d— collision: 2 issues each lead with this number: #107, #455.AD-563— collision: 2 issues each lead with this number: #10, #34.AD-568a— collision: 2 issues each lead with this number: #17, #30.AD-572— collision: 2 issues each lead with this number: #123, #359.AD-574— collision: 2 issues each lead with this number: #6, #361.AD-580— collision: 3 issues each lead with this number: #112, #127, #1143.AD-581— collision: 2 issues each lead with this number: #113, #468.AD-582— collision: 2 issues each lead with this number: #114, #128.AD-583f— collision: 2 issues each lead with this number: #117, #464.AD-589— collision: 2 issues each lead with this number: #153, #195.AD-594b— collision: 2 issues each lead with this number: #161, #472.AD-594d— collision: 2 issues each lead with this number: #163, #473.AD-605— collision: 3 issues each lead with this number: #181, #189, #487.AD-607— collision: 2 issues each lead with this number: #183, #488.AD-632d— collision: 2 issues each lead with this number: #235, #236.AD-632e— collision: 2 issues each lead with this number: #239, #240.AD-632f— collision: 2 issues each lead with this number: #237, #238.AD-633— collision: 2 issues each lead with this number: #228, #489.AD-641— the trackers disagree: deferred, shipped. Resolved asshipped.AD-641g— collision: 2 issues each lead with this number: #403, #430.AD-654d— collision: 2 issues each lead with this number: #326, #333.AD-660b— collision: 2 issues each lead with this number: #411, #460.AD-673— collision: 2 issues each lead with this number: #356, #370.AD-674— collision: 2 issues each lead with this number: #362, #371.AD-675— collision: 2 issues each lead with this number: #363, #372.AD-676— collision: 2 issues each lead with this number: #364, #373.AD-677— collision: 2 issues each lead with this number: #365, #374.AD-678— collision: 2 issues each lead with this number: #366, #375.AD-679— collision: 2 issues each lead with this number: #367, #376.AD-683— collision: 2 issues each lead with this number: #313, #419.AD-690— collision: 3 issues each lead with this number: #384, #417, #506.AD-691— collision: 2 issues each lead with this number: #385, #420.AD-697— collision: 3 issues each lead with this number: #428, #429, #431.AD-705— the trackers disagree: shipped, superseded. Resolved assuperseded.AD-705a— collision: 2 issues each lead with this number: #554, #555.AD-706c— collision: 3 issues each lead with this number: #518, #642, #643.AD-718d— collision: 2 issues each lead with this number: #525, #553.AD-720a— collision: 2 issues each lead with this number: #549, #562.AD-720d— collision: 5 issues each lead with this number: #552, #563, #564, #565, #645.AD-721— code is in history but #530, #538 is still open.AD-721b— collision: 6 issues each lead with this number: #529, #540, #559, #560, #561, #663.AD-721d— collision: 9 issues each lead with this number: #531, #541, #618, #619, #620, #621, #622, #623, #658.AD-721i— collision: 3 issues each lead with this number: #537, #542, #543.AD-722— collision: 4 issues each lead with this number: #544, #545, #572, #578.AD-722a— collision: 15 issues each lead with this number: #567, #573, #604, #605, #606, #607, #608, #609, #610, #611, #612, #613, #614, #615, #624.AD-722b— collision: 17 issues each lead with this number: #568, #574, #592, #593, #594, #595, #596, #597, #598, #599, #600, #601, #602, #603, #655, #657, #659.AD-722c— collision: 3 issues each lead with this number: #569, #575, #654.AD-722d— collision: 2 issues each lead with this number: #570, #576.AD-722e— collision: 3 issues each lead with this number: #571, #577, #644.AD-722f— collision: 2 issues each lead with this number: #579, #580.AD-723a— collision: 4 issues each lead with this number: #616, #617, #625, #626.AD-724— collision: 5 issues each lead with this number: #582, #627, #628, #629, #1264.AD-730— collision: 9 issues each lead with this number: #630, #631, #632, #633, #634, #635, #646, #647, #656.AD-733— collision: 3 issues each lead with this number: #641, #667, #668.AD-733c— collision: 4 issues each lead with this number: #675, #676, #677, #678.AD-742a— collision: 3 issues each lead with this number: #669, #679, #680.AD-749— collision: 2 issues each lead with this number: #686, #695.AD-750— collision: 2 issues each lead with this number: #687, #696.AD-752— collision: 2 issues each lead with this number: #688, #698.AD-753— collision: 2 issues each lead with this number: #689, #699.AD-754— collision: 2 issues each lead with this number: #690, #700.AD-755— collision: 2 issues each lead with this number: #691, #701.AD-756— collision: 2 issues each lead with this number: #692, #702.AD-757— collision: 2 issues each lead with this number: #693, #703.AD-758— collision: 2 issues each lead with this number: #694, #704.AD-817— collision: 2 issues each lead with this number: #747, #749.AD-819— collision: 2 issues each lead with this number: #752, #761.AD-820— collision: 2 issues each lead with this number: #753, #772.AD-822— the trackers disagree: allocated-open, shipped. Resolved asshipped.AD-822— collision: 2 issues each lead with this number: #755, #756.AD-825— collision: 3 issues each lead with this number: #760, #764, #771.AD-840— collision: 2 issues each lead with this number: #815, #819.AD-841— the trackers disagree: allocated-open, shipped. Resolved asshipped.AD-841— collision: 2 issues each lead with this number: #816, #820.AD-842— collision: 2 issues each lead with this number: #817, #821.AD-843— collision: 2 issues each lead with this number: #818, #822.AD-854— code is in history but #1131 is still open.AD-861— collision: 2 issues each lead with this number: #831, #1247.AD-909— collision: 2 issues each lead with this number: #872, #951.AD-938— the trackers disagree: allocated-open, shipped. Resolved asshipped.AD-943— collision: 2 issues each lead with this number: #874, #878.AD-944— collision: 2 issues each lead with this number: #875, #879.AD-945— collision: 2 issues each lead with this number: #876, #880.AD-946— collision: 2 issues each lead with this number: #877, #881.AD-983— the trackers disagree: deferred, shipped. Resolved asshipped.AD-985— the trackers disagree: allocated-open, shipped. Resolved asshipped.AD-1138— code is in history but #1057 is still open.AD-1143— code is in history but #1057, #1064 is still open.AD-1146— code is in history but #1068 is still open.AD-1166— collision: 2 issues each lead with this number: #1097, #1197.AD-1170— collision: 2 issues each lead with this number: #1101, #1257.AD-1179— the trackers disagree: allocated-open, shipped. Resolved asshipped.AD-1179— code is in history but #1111 is still open.AD-1183— code is in history but #1118 is still open.AD-1185— code is in history but #1121, #1138 is still open.AD-1203— code is in history but #1153 is still open.AD-1204— code is in history but #1163 is still open.AD-1224— code is in history but #1190 is still open.AD-1230— collision: 2 issues each lead with this number: #1203, #1256.AD-1241— code is in history but #1216 is still open.AD-1256— code is in history but #1302 is still open.AD-1258— code is in history but #1308 is still open.AD-1259— code is in history but #1309 is still open.AD-1270— the trackers disagree: allocated-open, shipped. Resolved asshipped.AD-1270— code is in history but #1324 is still open.AD-1276— code is in history but #1330 is still open.BF-063— collision: 2 issues each lead with this number: #3, #135.BF-125— collision: 2 issues each lead with this number: #28, #29.BF-126— collision: 2 issues each lead with this number: #33, #133.BF-133— collision: 2 issues each lead with this number: #116, #134.BF-145— collision: 2 issues each lead with this number: #158, #159.BF-183— collision: 2 issues each lead with this number: #245, #246.BF-184— collision: 2 issues each lead with this number: #247, #248.BF-185— collision: 2 issues each lead with this number: #249, #250.BF-186— collision: 2 issues each lead with this number: #251, #252.BF-187— collision: 2 issues each lead with this number: #253, #255.BF-188— collision: 2 issues each lead with this number: #254, #255.BF-189— collision: 2 issues each lead with this number: #256, #257.BF-190— collision: 2 issues each lead with this number: #259, #261.BF-193— collision: 2 issues each lead with this number: #263, #264.BF-207— collision: 2 issues each lead with this number: #282, #345.BF-236— the trackers disagree: allocated-open, shipped. Resolved asshipped.BF-264— collision: 2 issues each lead with this number: #422, #636.BF-623— the trackers disagree: allocated-open, shipped. Resolved asshipped.BF-687— code is in history but #1087 is still open.BF-701— code is in history but #1111 is still open.BF-706— code is in history but #1111 is still open.BF-707— collision: 2 issues each lead with this number: #1113, #1312.BF-711— code is in history but #1138 is still open.BF-759— collision: 2 issues each lead with this number: #1217, #1219.BF-779— code is in history but #1242 is still open.BF-790— code is in history but #1277 is still open.BF-794— code is in history but #1258 is still open.BF-795— code is in history but #1259 is still open.BF-803— code is in history but #1267 is still open.BF-811— code is in history but #1275 is still open.BF-813— code is in history but #1277 is still open.BF-814— code is in history but #1278 is still open.BF-817— code is in history but #1281 is still open.BF-824— code is in history but #1316 is still open.BF-840— code is in history but #1314 is still open.BF-844— code is in history but #1314 is still open.BF-846— code is in history but #1316 is still open.BF-858— code is in history but #1328 is still open.BF-861— code is in history but #1331 is still open.
Unparseable lines¶
9 head-shaped lines could not be parsed. A malformed or historical entry is skipped and counted, never fatal — five eras of formatting conventions are represented in these files.
PROGRESS.md:1063 head-shaped line yielded no AD/BF token
PROGRESS.md:1069 head-shaped line yielded no AD/BF token
progress-era-3-product.md:146 head-shaped line yielded no AD/BF token
progress-era-3-product.md:167 head-shaped line yielded no AD/BF token
progress-era-3-product.md:190 head-shaped line yielded no AD/BF token
progress-era-4-evolution.md:15 head-shaped line yielded no AD/BF token
progress-era-4-evolution.md:24 head-shaped line yielded no AD/BF token
progress-era-4-evolution.md:32 head-shaped line yielded no AD/BF token
progress-era-4-evolution.md:48 head-shaped line yielded no AD/BF token