Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 13 additions & 3 deletions spacecraft-accessibility-support/references/audit.md
Original file line number Diff line number Diff line change
Expand Up @@ -194,7 +194,17 @@ Report audit results with §17 progress format when the audit is part of an
implementation effort:

```
[Progress: ▰▰▰▰▰▰▰▰▰▰▰▰▰▰▱▱▱▱▱▱] 70%
Milestones: M0: 100% | M1: 100% | M2: 70% | M3: 0%
Product Status: MVP: 90% | PRD: 70%
M0: [████████████████████] 100%

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Rebuild the accessibility skill bundles

The reporting reference is changed here, but neither spacecraft-accessibility-support.zip nor .skill is updated; extracting either artifact still returns the previous three-line progress example. Users installing this skill from its bundles therefore continue receiving obsolete guidance, so rebuild and commit both artifacts with the reference change.

AGENTS.md reference: AGENTS.md:L95-L98

Useful? React with 👍 / 👎.

M1: [████████████████████] 100%
M2: [██████████████░░░░░░] 70%
M3: [░░░░░░░░░░░░░░░░░░░░] 0%
MVP: [ ▰▰▰▰▰▰▰▰▰▰▰▰▰▰▰▰▰▰▱▱ ] 90%
PRD: [██████████████░░░░░░] 70%
```

One row per track, each with its own 20-cell bar: milestone rows first,
then `MVP`, then whichever of `TODO`/`PLAN`/`PRD` the audit is driven by.
Emit only the rows that apply — never pad the block with 0% rows for
tracks that do not exist. `MVP` uses `▰`/`▱` with a space inside each
bracket; every other row uses `█`/`░` with tight brackets, and the
padding is what keeps the columns aligned.
45 changes: 37 additions & 8 deletions spacecraft-standard-constitution/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ description: >
Spacecraft Software-umbrella project — even if the user doesn't explicitly mention the Standard.
If the user mentions "Spacecraft Software", a Spacecraft Software subproject name, or asks you to work on
anything in the Spacecraft Software ecosystem, consult this skill immediately. It encodes
The Steelbore Standard v1.46 (§13 design systems; §3.1.1 TypeScript; §5.7 AGENTS.md; §6.4 contribution targets; §5.6 skill packaging; §11 palettes + §11.6 system theme; §18 accessibility; §17 progress reporting; §3.2 compiler flags; concurrency; §3.3 security-by-design) so
The Steelbore Standard v1.47 (§13 design systems; §3.1.1 TypeScript; §5.7 AGENTS.md; §6.4 contribution targets; §5.6 skill packaging; §11 palettes + §11.6 system theme; §18 accessibility; §17 progress reporting; §3.2 compiler flags; concurrency; §3.3 security-by-design) so

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Rebuild the standard skill bundles

This commit updates the standard source to v1.47 and changes its changelog, but both spacecraft-standard-constitution.zip and .skill remain byte-identical to the parent commit; extracting them still yields the v1.46 SKILL.md, old §17 format, and old changelog. Because these bundles are the installation surface, bundled consumers will not receive this update, so rebuild and commit both artifacts.

AGENTS.md reference: AGENTS.md:L95-L98

Useful? React with 👍 / 👎.

you never need to ask for it or have it attached to a prompt again.
license: GPL-3.0-or-later
maintainer: Mohamed Hammad <Mohamed.Hammad@SpacecraftSoftware.org>
Expand All @@ -17,7 +17,7 @@ website: https://Construct.SpacecraftSoftware.org/

# The Steelbore Standard — Compliance Reference

**Version:** 1.46 | **Date:** 2026-08-08 | **Author:** Mohamed Hammad
**Version:** 1.47 | **Date:** 2026-08-09 | **Author:** Mohamed Hammad
**Maintainer:** Mohamed Hammad | **Contact:** [Mohamed.Hammad@SpacecraftSoftware.org](mailto:Mohamed.Hammad@SpacecraftSoftware.org)
**Copyright:** Copyright (C) 2026 Mohamed Hammad & Spacecraft Software | **License:** GPL-3.0-or-later
**Website:** [https://Construct.SpacecraftSoftware.org/](https://Construct.SpacecraftSoftware.org/)
Expand Down Expand Up @@ -1486,18 +1486,47 @@ When implementing features or writing code based on a Product Requirements Docum

### §17.1 — Progress Reporting Format

Every progress report must include the percentage of completion for individual milestones, the overall progress of the Minimum Viable Product (MVP), and the total progress of the PRD.
A progress report is a block of labelled rows, one row per tracked track. Every row carries its own 20-cell bar and its own percentage, so each figure is legible on its own line rather than compressed into a shared summary line.

**Format template:**
```
[Progress: ▰▰▰▰▰▰▰▰▰▰▰▰▰▰▱▱▱▱▱▱] 70%
Milestones: M0: 100% | M1: 100% | M2: 70% | M3: 0% | M4: 0%
Product Status: MVP: 90% | PRD: 70%
M0: [████████████░░░░░░░░] 60%
M1: [████████████░░░░░░░░] 60%
M2: [████████████░░░░░░░░] 60%
M3: [████████████░░░░░░░░] 60%
M4: [████████████░░░░░░░░] 60%
MVP: [ ▰▰▰▰▰▰▰▰▰▰▰▰▰▰▱▱▱▱▱▱ ] 70%
TODO: [████████████░░░░░░░░] 60%
PLAN: [████████████░░░░░░░░] 60%
PRD: [████████████░░░░░░░░] 60%
```

**Row order** is fixed: milestone rows `M0`…`Mn` in ascending order, then `MVP`, then `TODO`, then `PLAN`, then `PRD`.

**Only applicable rows are emitted.** The milestone rows match the milestones the plan actually defines — there is no fixed count, and `M0`–`M4` in the template above is an illustration, not a required set. `TODO`, `PLAN`, and `PRD` each appear only when the task is driven by such an artifact. `MVP` is always present. A row is never padded in at 0% to fill out the block: a fabricated track reports progress against nothing and misrepresents the work.

### §17.2 — Progress Bar Style

The progress bar must use high-visibility Unicode block characters (e.g., `▰` for filled and `▱` for empty) to form a clean, static, 20-character visual representation of total PRD completion. Do not use legacy ASCII characters like `#` or `-` for the progress bar.
Every bar is a static, 20-cell, high-visibility Unicode bar. Legacy ASCII characters — `#`, `-`, `=` — are forbidden in any bar.

Two cell styles are in use, and the distinction is normative:

| Rows | Filled | Empty | Brackets |
|------|--------|-------|----------|
| Milestones, `TODO`, `PLAN`, `PRD` | `█` (U+2588) | `░` (U+2591) | Tight — no space inside either bracket |
| `MVP` | `▰` (U+25B0) | `▱` (U+25B1) | Padded — exactly one space inside each bracket |

The MVP row is deliberately set apart: it is the headline figure, and the tracks above and below it are the inputs that feed it. Its distinct glyph pair makes it findable at a glance in a stack of otherwise identical bars.

**Column alignment is normative.** The MVP row's bracket padding exists to preserve it — the row is one character narrower in its label field and one character wider inside each bracket, so every bar cell and every percentage digit lands in the same column across the whole block.

- On every row other than `MVP`, the label and its colon are left-aligned in a six-character field, followed immediately by `[`.
- On the `MVP` row, `MVP:` is left-aligned in a five-character field, followed by `[` and one space.
- Both place the first bar cell in column 8, so every bar occupies columns 8 through 27.
- The percentage is right-aligned so its `%` sign lands in the same column on every row — two spaces after the closing bracket on the tight-bracket rows, one on the `MVP` row. That difference is exactly what the padded brackets buy.
- The separator never drops below one space. At 100% the `MVP` row keeps its single space and its percentage therefore sits one column right — the only value at which the two row types do not align, and preferable to a bracket abutting a digit.

**Cell count.** The number of filled cells is the percentage scaled to twenty cells and rounded to the nearest cell. Two saturation rules override the rounding: a bar shows twenty filled cells **only** at exactly 100%, and zero filled cells **only** at exactly 0%. Rounding 99% up to a visually complete bar reports work as finished that is not, which is the drift this chapter exists to catch.

### §17.3 — Reporting Cadence

Expand Down Expand Up @@ -1721,7 +1750,7 @@ Before finalising **any** Spacecraft Software artifact, mentally verify:
- [ ] **§14** ISO 8601 dates; 24h time; UTC Z is the default primary timestamp (companion local time with UTC offset permitted, never a replacement) — unless the project filed the §14.2.1 domain exception for inherently local-time-bound data; ISO 8601 durations; metric units
- [ ] **§15** Attribution present: maintainer name (`Mohamed Hammad`), contact (`Mohamed.Hammad@SpacecraftSoftware.org`), and project URL in `--version` / README / About
- [ ] **§15.3** Third-party work credited in `CREDITS.md` at project/skill root when triggers apply; deeper `references/ATTRIBUTION.md` present where reference content is adapted from external sources
- [ ] **§17** Development progress tracked and reported continuously with milestone percentages, MVP, total PRD completion, and a Unicode progress bar
- [ ] **§17** Development progress tracked and reported continuously as the §17.1 labelled-row block — one 20-cell bar per track, milestone rows then MVP then TODO/PLAN/PRD, only the rows that apply; MVP set in `▰`/`▱` with padded brackets and every other row in `█`/`░`, columns aligned, no ASCII bars
- [ ] **§18** Accessible mode implemented and off by default; §18.1 toggle honored with correct precedence; status never color-only; no animation or decorative art in accessible mode; TUI ships a linear mode and a non-interactive CLI path; GUI publishes accessible names and roles (AccessKit for Rust); verified with a real screen reader; existing projects carry a dated remediation entry in `PROJECTS.md` until they conform — N/A for projects registered as games (§18.5), which are exempt in full
- [ ] **§6.3** All commits to Spacecraft Software Git remotes cryptographically signed with the `Mohamed.Hammad@SpacecraftSoftware.org` key and showing "Verified" on the hosting platform; rewrites preserve signatures; programmatic and assistant-driven commits signed too
- [ ] **§6.4** No commit, pull request, patch, issue, or package publication sent to a namespace outside `Spacecraft-Software` / `UnbreakableMJ` without explicit per-contribution maintainer authorization; automation, CI, and assistant-driven work never initiate an outbound contribution
Expand Down
Loading
Loading