diff --git a/STATUS.md b/STATUS.md index e31a6dd..d54305b 100644 --- a/STATUS.md +++ b/STATUS.md @@ -1,6 +1,6 @@ # STATUS โ€” automotive-skills-suite -_Auto-generated 2026-06-07 by automotive-skills-daily-standup._ +_Auto-generated 2026-06-08 by automotive-skills-daily-standup._ | Builder | Domain | Paired Reviewer | Last Touched | Flag | |---------|--------|-----------------|--------------|------| @@ -86,5 +86,5 @@ _Auto-generated 2026-06-07 by automotive-skills-daily-standup._ - Builders: **76**, Reviewers: **76**, Paired ratio: **100.0%** - ๐ŸŸข Paired & fresh (โ‰ค30d): **2** ยท ๐ŸŸก Stale (>30d): **74** ยท ๐Ÿ”ด Orphan builders: **0** - Domain spread: safety=15, quality=10, comms=8, cyber=6, autosar=5, diagnostics=5, program-mgmt=5, v&v=5, aspice=4, sysml=4, calibration=3, mbse=3, sotif=3 -- Date: 2026-06-07 +- Date: 2026-06-08 - Source: scan of `skills/` directory + `git log -1` per file. diff --git a/docs/AUTONOMOUS_LOG.md b/docs/AUTONOMOUS_LOG.md index d65bcab..947a3d7 100644 --- a/docs/AUTONOMOUS_LOG.md +++ b/docs/AUTONOMOUS_LOG.md @@ -471,3 +471,18 @@ Standout finding is non-DoD and more impactful than the trigger gaps: the SKILL. - Mon W24 PLAN: include one SOTIF target (sotif-analysis or triggering-conditions) โ€” zero-touch domain in May. - #11 (packaging utility, external patch attached) needs a human decision โ€” it's been open since 2026-05-22 with a ready patch; bot policy is not to merge external code. - Fmeda medium findings (classification-ladder branch, SMvDU acronym, 100x unit convention) still await maintainer action. + +## 2026-06-08 (autonomous run, PLAN) + +**Mode:** PLAN +**Action:** W24 plan written (docs/weekly/WEEK-2026-W24.md), 5 fresh tracking issues created (#19โ€“#23), STATUS.md regenerated. +**Files touched:** STATUS.md, docs/weekly/WEEK-2026-W24.md, docs/AUTONOMOUS_LOG.md (this entry) +**Tests:** N/A (no test suite in this repo yet) +**Skill count:** 76 builders / 76 reviewers / 100% paired +**Open issues:** 5 (all created this run; tracker was at 0 on entry) +**Notes:** The headline event is an external tracker reset โ€” Sunday's TRIAGE recorded 12 open issues, but this morning the GitHub API returns `open_issues_count = 0`: a maintainer closed the entire backlog (#3โ€“#12, #15, #16) over the weekend, including the four-week carryovers #4 (cs-concept) and #5 (aspice-assessment), tooling #10/#11. Judgement calls: (1) With no open issues, the standup priority order falls through (a) "issue-referenced skills" to (c) least-recently-touched builders; I picked for maximum domain spread across the stale ๐ŸŸก cohort (sotif/safety/quality/comms) plus one tooling slot. (2) I deliberately did NOT re-enqueue #4/#5 as polish loops โ€” three weeks of journals recommended converting them to maintainer-PR targets, and the human closing them is read as a decision to end the loop, not reopen it; their ready rewrites stay in the polish log for a future maintainer PR. (3) SOTIF mandate honored (#20) โ€” May's only zero-touch domain. (4) Classifier extraction re-filed fresh as #19 (successor to closed #10); the inline override map is stable at 9 entries and ready to freeze โ€” this would otherwise be the 10th consecutive hand-maintained regen. (5) Issue numbers jumped to #19โ€“#23 (tracker had passed #13/#14/#17/#18 via external activity). STATUS regen reproduced the canonical spread (safety=15, quality=10); only the two date lines changed vs. yesterday. +**Follow-ups:** +- Tue W24 POLISH: prioritize #19 (scripts/classify_skill.py) โ€” highest-value debt retirement; explicit map is frozen at 9 entries and documented in the issue body. After it lands, every future STATUS regen is `python scripts/classify_skill.py > STATUS.md`. +- Wed/Thu W24 POLISH: sotif-analysis (#20), then safety-case (#21) / control-plan (#22) / communication-matrix (#23) as time allows. Expect ~3 of 4 skill targets to land in-week. +- Confirm with maintainer (or via next TRIAGE) whether the weekend mass-close means the polish-loop workflow itself should change โ€” if the human is closing weekly-target issues without merging the polish-log rewrites, the value of opening them weekly is worth revisiting. +- The fmeda medium findings from W23 (classification-ladder branch, SMvDU acronym, 100ร— unit convention) and the cs-concept/tara findings still sit in the polish logs unapplied; none have an open issue anymore. Flag for human: decide whether these become PRs or are dropped. diff --git a/docs/weekly/WEEK-2026-W24.md b/docs/weekly/WEEK-2026-W24.md new file mode 100644 index 0000000..db03f7d --- /dev/null +++ b/docs/weekly/WEEK-2026-W24.md @@ -0,0 +1,80 @@ +# Week 2026-W24 โ€” Plan + +_Auto-generated 2026-06-08 by automotive-skills-daily-standup (PLAN run)._ + +## Recap โ€” past 7 days + +``` +d8b19ef auto(triage): label refresh, #12 typed, #17 delta confirmed, STATUS regen +8e826bb auto(release): v2026.06.W23 weekly snapshot, RELEASES.md, CHANGELOG roll, STATUS regen +c21a84a auto(docs): W23 changelog roll, 3 example stubs, STATUS regen +d6afa26 auto(polish): W23 #3 fmeda-builder pass, regen STATUS, journal +22d6409 auto(polish): W23 #2 tara-builder pass, regen STATUS, journal +5b4b006 auto(polish): W23 #1 cs-concept-builder pass, regen STATUS, journal +f8e940f auto(monthly): KPI report for May 2026 +3af1f6b auto(plan): W23 targets โ€” cs-concept, aspice-assessment, classifier, fmeda, tara +``` + +W23 closed clean: tag `v2026.06.W23` pushed, RELEASES.md drafted for manual +Publish, 100% paired ratio (76/76) held. Three W23 polish passes landed +(cs-concept, tara, fmeda) plus 3 example stubs and the May monthly KPI. + +**Tracker reset.** Sunday's TRIAGE recorded 12 open issues. As of this +PLAN run the GitHub API reports `open_issues_count = 0` โ€” **a maintainer +closed every open issue** (#3โ€“#12, #15, #16) between Sun and Mon. This +clears the entire backlog the prior PLAN/POLISH cadence was anchored on, +including the four-week carryovers #4 (cs-concept) and #5 (aspice-assessment) +and the tooling debt #10 (classifier) and #11 (packaging utility). The +standup priority order therefore falls through (a) "skills referenced by +open issues" โ†’ none โ†’ to (c) least-recently-touched builders, with the +standing journal mandates (SOTIF coverage, classifier extraction) folded in. + +## W24 targets + +Suite is 100% paired (76/76), zero orphan builders. With the issue tracker +emptied, targets are drawn from the stale ๐ŸŸก cohort (74 builders untouched +since 2026-05-01/02) for maximum domain spread, plus one tooling slot to +finally retire the long-running inline-classifier debt. Fresh issues +created this run; the human-closed carryovers (#4/#5) are deliberately +**not** re-enqueued as polish loops (see Notes). + +| # | Target | Domain | Tracking issue | Definition of done | +|---|---|---|---|---| +| 1 | scripts/classify_skill.py extraction | tooling | #19 (successor to closed #10) | Extract inline STATUS-regen logic (domain inference + alias map + flag rules + 9-entry explicit override) into `scripts/classify_skill.py`; standup regenerates via `python scripts/classify_skill.py > STATUS.md`. DoD: output byte-matches current canonical spread; STATUS section of standup shrinks to one shell line. | +| 2 | sotif-analysis-builder.skill | sotif | #20 | Fresh W24-dated polish-log entry; description char-count + frontmatter audited; small obvious fixes applied in-place; severity logged. Satisfies the standing SOTIF-coverage mandate (only zero-touch domain in May KPI). | +| 3 | safety-case-builder.skill | safety | #21 | Fresh W24-dated polish-log entry; description char-count + frontmatter audited; small obvious fixes applied in-place; severity logged. ISO 26262-2 capstone integrator, densest domain, never polished. | +| 4 | control-plan-builder.skill | quality | #22 | Fresh W24-dated polish-log entry; description char-count + frontmatter audited; small obvious fixes applied in-place; severity logged. Quality-domain anchor (AIAG Control Plan), stale since 2026-05-01. | +| 5 | communication-matrix-builder.skill | comms | #23 | Fresh W24-dated polish-log entry; description char-count + frontmatter audited; small obvious fixes applied in-place; severity logged. Central comms artifact, stale since 2026-05-02. | + +All five tracking issues were created fresh this run (#19โ€“#23); the issue +tracker had jumped past #13/#14/#17/#18 from external activity, consistent +with prior journal notes. + +## Domain-spread check + +Targets span 4 distinct skill domains plus tooling: sotif (ร—1), safety (ร—1), +quality (ร—1), comms (ร—1), tooling (ร—1). No domain is doubled โ€” a deliberate +spread across the stale cohort. Polish passes land Tue/Wed/Thu, so expect +~3 of the 4 skill targets to execute in-week; the tooling slot (#19) is the +priority Tuesday pick. Carryover lands on the W25 backlog. + +## Notes / judgement calls + +- **Do not re-enqueue #4/#5.** The four-week carryovers cs-concept (#4) and + aspice-assessment (#5) were closed by the maintainer this weekend along + with the rest of the backlog. Prior journals recommended converting them + to maintainer-PR targets; the human closing them is read here as a + decision to stop the polish loop, not an invitation to reopen it. Their + ready-to-apply rewrites remain in `docs/skill-polish-log/` for any future + maintainer PR. W24 picks fresh stale targets instead. +- **Classifier extraction is now its own fresh issue (#19).** Closed #10 + is its predecessor. This is the 10th run the inline map would otherwise be + hand-maintained; the explicit override is stable at 9 entries and ready to + freeze into `scripts/classify_skill.py`. Prioritized as the Tuesday slot. +- **SOTIF mandate honored** via #20 (sotif-analysis-builder). May was the + only zero-touch SOTIF month per the monthly KPI; landing one SOTIF polish + in W24 prevents a second. +- **Tag scheme** (a RELEASE concern, flagged four times in W23 journals) + resolved by default to ISO-absolute (`v2026.06.W23` shipped Saturday). + W24's Saturday RELEASE, if commits warrant, continues the ISO-absolute + series as `v2026.06.W24`. No further PLAN action.