From cd154c0ce965ad5cb982409e78238251e1cfdf7e Mon Sep 17 00:00:00 2001 From: UnbreakableMJ Date: Wed, 24 Jun 2026 10:55:07 +0300 Subject: [PATCH] =?UTF-8?q?feat(standard):=20sync=20=C2=A73.2=20concurrenc?= =?UTF-8?q?y=20reframe=20to=20skill=20=E2=80=94=20v1.30?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Mirrors the Standard v1.30 §3.2 rewrite: opens with the modern-hardware rationale (multi-core/multi-thread is universal; harness it), frames concurrency as an architecture-level concern (ground-up design, not bolted-on optimization), and makes adoption/abandonment conditions explicit (adopt where it advances performance; abandon where it degrades performance or compromises Priority 1 Stability). Compliance-checklist bullet and frontmatter description updated to v1.30. Co-Authored-By: Claude Sonnet 4.6 --- spacecraft-standard/SKILL.md | 23 +++++++++++++-------- spacecraft-standard/references/CHANGELOG.md | 1 + 2 files changed, 15 insertions(+), 9 deletions(-) diff --git a/spacecraft-standard/SKILL.md b/spacecraft-standard/SKILL.md index c2df1d3..ad03819 100644 --- a/spacecraft-standard/SKILL.md +++ b/spacecraft-standard/SKILL.md @@ -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.29 (Texinfo source pipeline; §2.1 Aetheric+Ferrocast Deprecated; §15.1 Vacuum+Loran Pages subdomains; §3.3 Security by Design; §8 Texinfo; §7 Shell Environment) so + 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 you never need to ask for it or have it attached to a prompt again. license: GPL-3.0-or-later maintainer: Mohamed Hammad @@ -17,7 +17,7 @@ website: https://Construct.SpacecraftSoftware.org/ # The Steelbore Standard — Compliance Reference -**Version:** 1.29 | **Date:** 2026-06-23 | **Author:** Mohamed Hammad +**Version:** 1.30 | **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/) @@ -148,12 +148,17 @@ not the whole of Priority 1.** and fuzz/property where applicable) gating CI, not asserted by inspection alone. ### §3.2 — Priority 2: Performance -Performance is the foremost priority after stability. The default means of achieving it is -**multi-core, multi-thread concurrency** — parallelism is the expected baseline, not an -afterthought — *unless* concurrency would materially degrade performance (synchronization -overhead, lock contention, or inherently serial / small workloads outweighing the gains), -in which case a simpler or serial approach must be chosen and the trade-off documented. -- Concurrency must be **designed-in from the start**, never bolted on retroactively. +Performance is the foremost priority after stability. Modern hardware universally provides +**multi-core, multi-thread** capability; harnessing that concurrency is the primary means of +achieving performance. Concurrency is not an afterthought — it must be **considered from the +ground up**, throughout architecture design: data ownership, thread boundaries, synchronization +points, and parallelism opportunities must be identified during design, not discovered during +optimization. + +Concurrency is adopted where it genuinely advances performance. It is **abandoned** where it +degrades performance (synchronization overhead, lock contention, or inherently serial / small +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 @@ -832,7 +837,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: multi-core/multi-thread concurrency by default (or serial trade-off documented); concurrency designed-in; 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; 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/` diff --git a/spacecraft-standard/references/CHANGELOG.md b/spacecraft-standard/references/CHANGELOG.md index 3aed114..580ec5b 100644 --- a/spacecraft-standard/references/CHANGELOG.md +++ b/spacecraft-standard/references/CHANGELOG.md @@ -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.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`. - **v1.27 (2026-06-22):** **§15.1:** registered the **Loran Pages** subdomain (`Loran-Pages.SpacecraftSoftware.org`). The `loran-pages` repo — community catalog of curated Loran help pages (tldr-pages-style, `loran validate` CI gate, minisign-signed `publish.yml`) — created private with §5.2 posture files and §4.3 REUSE compliance.