Bump README, FEATURES, FOR_RECRUITERS, ROADMAP, and GRIMOIRE from the v60
"Sun & Salt" line to the v80 "Sunlance" 1.0 GA milestone.
- Version strings, badges, and headline metrics -> v80 / 1.0 GA
- ALFRED v5 -> v6.0; GRIMOIRE 100 labs -> 108 (catalog 1.0); 160 -> 209 crates
- Post-quantum framed as the default posture
- Correct the now-dead custom-syscall claim (469-485 collide with upstream
Linux 6.19) -> generic capability-gated, signed kernel-module interface
- Generalize stale CI-workflow / kernel-module counts
IP discipline: withholds v61-v80 subsystem internals (consensus, federated
learning, policy engine, cross-prompt-injection, char-dev/ioctl specifics,
key-escrow). Public-safe pre-release information only.
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
GRIMOIRE.md additions:
- The arsenal — three distrobox-based operator environments (Kali,
BlackArch's 2,800+ packages, Parrot privacy stack), 600+ host-native
tools via pacman/AUR, ~3,400 cross-distrobox total, with progressive
unlock through certification arcs
- Boss contracts — raids vs nightmare tiers, contract.toml state
machine semantics, branch-on-solution-approach, faction favor as
earned reputation
- The XP engine — ~100K-line gamification crate, modified-logarithmic
level curve with prestige boundaries, multiplicative multiplier stack
(property-tested cap), signed-commit-attestation XP for upstream
contributions (forge-resistant)
- Loot economy depth — tier-tied drop tables, prestige-locked gear,
reputation multipliers
- Certification arcs — OffSec (OSCP/OSEP/OSWE/OSCE³), GIAC, ISC²,
EC-Council, INE, Splunk/Sentinel/Elastic, AZ-500/SC-100/AWS Security
- Blue + red + purple split — full-spectrum positioning vs the
curriculum-only competitors
MESH.md (NEW) — the e-waste reduction philosophy as a load-bearing
front-door doc. Three reinforcing pillars (environmental, economic,
sovereign) + how the mesh works at a high level + what it enables.
"The mesh is the product. Everything else is architecture in service
of this core." Old laptops and retired workstations pulled from the
e-waste stream back into a sovereign compute pool.
README.md updates:
- Mesh-on-salvaged-silicon as a first-class capability bullet
- Promise section now leads with "the mesh is the product"
- Cross-link to MESH.md
The pivot here is from "Syn_OS is a security distro with mesh capability"
to "Syn_OS is mesh-of-old-hardware running local AI; security distro is
how we got here." This matches the founder's stated load-bearing thesis.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Visual identity for the public-facing repo:
- Phoenix logo (red, with Syn_OS wordmark) at the top of README as hero
- Phoenix-white variant in the footer band for visual symmetry
- Sanctum wallpaper added to assets/ (available for embed where useful)
- Four no-fake-stats badges: pre-release status, Sun & Salt codename,
Rust language tag, CC-BY-SA docs license
Assets directory created at assets/ holding only what's safe to publish:
phoenix.png, phoenix-white.png, synos-sanctum.png. Live desktop
screenshot and oversized wallpapers omitted (privacy + repo size).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Front-door + product-surface files (README, GRIMOIRE, FEATURES,
FOR_RECRUITERS) keep their concrete v60 content — these are the pages
that need to project ambition and inform potential users / cohorts /
recruiters.
Three files trimmed to vague:
- ARCHITECTURE.md — drop syscall numbers (469-485), specific module
names, "11-region brain", "83.54% Rust", "8-node Tailscale mesh".
Keep the synaptic gap framing, four pillars by name, three-image
table, axioms. Specs invite "well actually" issues; philosophy
doesn't.
- ROADMAP.md — keep v60 as the current generation marker, drop the
v44–v60 codesprint table (16 codenamed campaigns is a lot of
fact-checkable claims), drop the explicit v61–v70 horizon bullets.
Replace with broad theme prose. "What we're heading into" rather
than "what we promise by when".
- CONTRIBUTING.md — drop the explicit "what's coming" promises (lab
marketplace, CVE channel, community calls, public source release
date). Drop the "open an issue with title X" workflows that invite
unbidden submissions. Keep the long-game framing and quiet-channels
posture.
Net: front-door pages still impress with specifics; the surfaces a
random reader might use to file noise issues now offer none of the
hooks for it.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
- README.md: Complete project overview with features, download, quick start
- ARCHITECTURE.md: System design, components, security architecture
- Includes technology stack, deployment models, performance specs
- All non-sensitive IP suitable for public consumption
