Skip to content

feat(standard): sync §3.2 compiler flags notation rule to skill — v1.31 #9

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
UnbreakableMJ merged 1 commit into from
Jun 24, 2026
Merged

feat(standard): sync §3.2 compiler flags notation rule to skill — v1.31 #9

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
19 changes: 11 additions & 8 deletions spacecraft-standard/SKILL.md
View file
Open in desktop
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.30 (§3.2 concurrency as architecture-level concern; modern hardware rationale; adoption/abandonment conditions explicit; Texinfo source pipeline; §3.3 Security by Design; §8 Texinfo; §7 Shell Environment) so
The Steelbore Standard v1.31 (§3.2 compiler flags: applied+disabled both explicitly noted; concurrency as architecture-level concern; modern hardware rationale; Texinfo source pipeline; §3.3 Security by Design; §8 Texinfo; §7 Shell Environment) so
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.30 | **Date:** 2026-06-24 | **Author:** Mohamed Hammad
**Version:** 1.31 | **Date:** 2026-06-24 | **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 @@ -160,11 +160,14 @@ degrades performance (synchronization overhead, lock contention, or inherently s
workloads) or where it would compromise Priority 1 (Stability). When a serial or simpler
approach outperforms or is safer, it must be chosen and the trade-off documented.
- Release builds should use CPU-optimized flags — `-march=native`, LTO, PGO —
**where the toolchain and target support them reliably.** Any such flag known to
break or destabilize builds on a given platform/toolchain/linker (e.g., LTO under
certain NixOS, cross-compilation, or static-linking setups) MUST be disabled and
the reason documented. Stability (P1) outranks Performance (P2) — never ship a
broken or unstable build for the sake of a flag.
**where the toolchain and target support them reliably.** **Every applied flag must
be explicitly noted** (e.g., a comment in the build file or a build-time message);
**every disabled flag and the reason for disabling must be equally noted.** Visible
flag state at compile time makes errors traceable to a specific flag. Any flag known
to break or destabilize a build on a given platform/toolchain/linker (e.g., LTO
under certain NixOS, cross-compilation, or static-linking setups) MUST be disabled.
Stability (P1) outranks Performance (P2) — never ship a broken build for the sake
of a flag.
- Benchmarking is **mandatory** before and after any optimization work; regressions must
be documented and justified — and it is the evidence by which the concurrency-vs-serial
trade-off above is decided.
Expand Down Expand Up @@ -837,7 +840,7 @@ Before finalising **any** Spacecraft Software artifact, mentally verify:

- [ ] **§2** Aerospace/Sci-Fi/AI naming convention applied to all **new** identifiers; legacy (pre-v1.2) names preserved unless explicitly renamed
- [ ] **§3.1** Stability: memory safety (Rust, or ASLR+CFI documented); robust error handling, fault tolerance, and test-verified
- [ ] **§3.2** Performance: concurrency considered throughout architecture design; adopted where it advances performance, abandoned where it degrades performance or compromises Stability; serial trade-off documented; benchmarking before/after
- [ ] **§3.2** Performance: concurrency considered throughout architecture design; adopted where it advances performance, abandoned where it degrades performance or compromises Stability; serial trade-off documented; compiler optimization flags applied/disabled with explicit notation; benchmarking before/after
- [ ] **§3.3** Hardened security; PQC readiness addressed
- [ ] **§4.1** License is `GPL-3.0-or-later` or `AGPL-3.0-or-later` (AGPL for network-facing; per §4.1)
- [ ] **§4.2** Upstream copyright notices, license texts, and `NOTICE`/`AUTHORS` preserved verbatim; upstream licenses shipped in `LICENSES/`
Expand Down
1 change: 1 addition & 0 deletions spacecraft-standard/references/CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,7 @@ holds the full history so it doesn't load into agent context on every skill
activation. The published Standard document (`standard/The_Steelbore_Standard.md`)
keeps its own inline changelog as the canonical record.

- **v1.31 (2026-06-24):** **§3.2** compiler optimization flag documentation rule extended — previously only *disabled* flags required documentation; now **both applied and disabled** flags must be explicitly noted (comment in build file or build-time message). Symmetrical notation makes the full flag state visible at compile time and makes build errors traceable to specific flags. Compliance-checklist §3.2 bullet updated.
- **v1.30 (2026-06-24):** **§3.2** reframed — modern hardware universally provides multi-core/multi-thread capability; harnessing that concurrency is the primary performance lever. Concurrency is now an **architecture-level concern**, considered from the ground up throughout design (not bolted on at implementation). Adoption/abandonment conditions explicit: embrace concurrency where it advances performance; abandon it where it degrades performance (overhead, contention, serial workloads) or compromises Priority 1 (Stability). Compliance-checklist §3.2 bullet revised.
- **v1.29 (2026-06-23):** **Source of truth switched to Texinfo** — `The_Steelbore_Standard.texi` is now the canonical source; `.md` and `.html` are generated outputs (`make md` / `make html`); `.docx`/`.odt` produced on request only. `Makefile` and `spacecraft.css` added. Skill Cross-References updated: "Authoring a Texinfo manual" row now points to `spacecraft-texinfo` skill; "DOCX/ODT/PDF" row clarified as on-demand. `source-format` metadata updated from `odt` to `texi`.
- **v1.28 (2026-06-23):** **§2.1:** corrected `Aetheric` (was Active) and `Ferrocast` (was Planning) to **Deprecated** — both superseded by other projects, matching their status in `PROJECTS.md`.
Expand Down
Loading