Skip to content
scsiwyg
sign insign up
get startedmcpcommunityapiplaygroundswaggersign insign up
Ai26.10 — AI-Enabled Autonomous Fermentation Control·Welcome to the Ai26.10 internal team site26 Apr 2026David Olsson
Ai26.10 — AI-Enabled Autonomous Fermentation Control

Welcome to the Ai26.10 internal team site

#announcement#onboarding

David OlssonDavid Olsson

This site is the internal command center for Ai26.10 — AI-Enabled Autonomous Fermentation Control System, our PIC-funded consortium project between Crush Dynamics Inc. (CDI) and Atomic47 Labs (A47).

What's here

The site has six surfaces, all live:

  • Dashboard — current phase, RAG health, budget, key dates, active milestones, critical risks. Pulled directly from .project-state/ in the repo.
  • Milestones — all 13 Schedule A milestones with planned dates, owners, completion criteria, and progress.
  • Risks — 12 tracked risks ranked by severity, with mitigation and contingency for each.
  • Decisions — the formal decisions log (ADRs in spirit).
  • Team — project members and their roles.
  • Baseline Reports — every document and workbook from the April 24 baseline, rendered inline. Originals downloadable.
  • Blog (this) — project updates, weekly notes, technical writeups.
  • Wiki — tree-organized reference content. Put long-lived knowledge here.

How updates flow

SurfaceAuthoringLive in
Dashboard / Milestones / Risks / Decisions / TeamEdit YAML in .project-state/ (use the project-state skill)≤5 min
Baseline ReportsDrop new docx/xlsx into Baseline-Reports-YYYY-MM-DD/Next deploy
Blogscsiwyg MCP publish_post to ai26-10≤5 min
Wikiscsiwyg MCP publish_wiki_page to ai26-10≤5 min

Everything reads with a 5-minute revalidation window, so changes propagate fast without a full redeploy.

What we need from the team

  • Weekly notes → publish here as a blog post tagged weekly.
  • Technical reference material that should outlive a single update → wiki.
  • Decisions you want recorded → decisions log (ask David or use the project-state skill).
  • Status updates on your milestones → update percent_complete and technical_progress in the milestone YAML.

If you spot something stale or wrong, ping the channel and we'll fix it.

Share
𝕏 Post