From 720a3ddb8b6c350fb9db5491f1489df932320794 Mon Sep 17 00:00:00 2001 From: znerol2 <6800371+znerol2@users.noreply.github.com> Date: Sat, 24 Oct 2026 14:23:08 +0200 Subject: [PATCH] docs(profile): voice-clean the org front page and correct two process facts Clear every em dash and contrast sentence from the org profile, including "(enforced, not aspirational)", and keep every link and the EBU disclaimer word for word. Two statements now match the working model: milestones schedule issues (the board is optional curation), and component-repo issues are triaged within about a week, then closed or linked to an umbrella issue. Refs dmfdeploy/dmfdeploy#688 Signed-off-by: znerol2 <6800371+znerol2@users.noreply.github.com> --- profile/README.md | 71 ++++++++++++++++++++++++++--------------------- 1 file changed, 39 insertions(+), 32 deletions(-) diff --git a/profile/README.md b/profile/README.md index 5c587bc..99d1cf5 100644 --- a/profile/README.md +++ b/profile/README.md @@ -11,51 +11,58 @@ https://github.com/user-attachments/assets/677f2278-1f5b-4bc5-9685-ae23d0a438ce > Facility* reference architecture, are for technical context and vocabulary > alignment only. -`dmfdeploy` is an open-source experiment that explores whether ideas from the -[EBU](https://tech.ebu.ch/) *Dynamic Media Facility* publications can be studied -on commodity infrastructure: k3s, Ansible, NetBox, AWX, Authentik, OpenBao, and -a React operator console. The current prototype drives a blank ARM64 node toward -a small, reproducible media-operations stack — identity, secrets custody, -source-of-truth inventory, and a deployable media-function catalog — through a -Day-0 installer container. +`dmfdeploy` is an open source experiment. It studies ideas from the +[EBU](https://tech.ebu.ch/) *Dynamic Media Facility* publications on commodity +infrastructure: k3s, Ansible, NetBox, AWX, Authentik, OpenBao, and a React +operator console. A Day-0 installer container takes a blank ARM64 node toward a +small, reproducible media-operations stack. The stack covers identity, secrets +custody, a source-of-truth inventory, and a catalog of deployable media +functions. **Proven so far** (first-party): NMOS IS-04/05 deploys and runs on commodity -ARM k3s, driven end-to-end through the platform's catalog control chain -(console → AWX → Helm → NetBox lifecycle state). The larger claim — that a -*stranger* can reproduce this — is what v0.1 is closing: +ARM k3s. The platform's catalog control chain drives it end to end, from the +console through AWX and Helm to the lifecycle state in NetBox. The larger claim +is that a *stranger* can reproduce this, and v0.1 is working to show it. For +the full argument, see [the thesis one-pager](https://github.com/dmfdeploy/dmfdeploy/blob/main/docs/THESIS.md). -**What v0.1 does not claim:** no production ST-2110/PTP/multicast -correctness, no real-time media-plant claims, no multi-node HA, no cross-site -federation, no performance numbers. Single-node is the proof surface; the rest -is named future work, not implied capability. +**What v0.1 does not claim:** production ST 2110, PTP, or multicast +correctness, real-time media-plant behavior, multi-node high availability, +cross-site federation, or performance numbers. +Single-node is the proof surface. The rest is named future work, and this page +doesn't claim it works today. ## Start here | You are… | Go to | |---|---| -| **Curious / evaluating** — "what is this and does it work?" | [THESIS](https://github.com/dmfdeploy/dmfdeploy/blob/main/docs/THESIS.md) → [dmf-init](https://github.com/dmfdeploy/dmf-init) (the Day-0 installer) | +| **Curious or evaluating:** "What is this, and does it work?" | [THESIS](https://github.com/dmfdeploy/dmfdeploy/blob/main/docs/THESIS.md) → [dmf-init](https://github.com/dmfdeploy/dmf-init) (the Day-0 installer) | | **A potential contributor** | [JOURNEY](https://github.com/dmfdeploy/dmfdeploy/blob/main/docs/JOURNEY.md) → [CONTRIBUTING](https://github.com/dmfdeploy/dmfdeploy/blob/main/CONTRIBUTING.md) → [Issues](https://github.com/dmfdeploy/dmfdeploy/issues) + [project board](https://github.com/orgs/dmfdeploy/projects/1) | -| **Working here with AI agents** | [WORKING-MODEL](https://github.com/dmfdeploy/dmfdeploy/blob/main/docs/WORKING-MODEL.md) — how Issues, milestones, the board, Discussions, and the doc rules fit together (enforced, not aspirational) | +| **Working here with AI agents** | [WORKING-MODEL](https://github.com/dmfdeploy/dmfdeploy/blob/main/docs/WORKING-MODEL.md): how Issues, milestones, the board, Discussions, and the doc rules fit together | -**[`dmfdeploy`](https://github.com/dmfdeploy/dmfdeploy) is the front door** — -the umbrella repo with the consolidated knowledge base, decision record (ADRs), -and cross-repo coordination. The eight `dmf-*` repos are the components; each -README describes its place in this project's reading of the EBU layer vocabulary. +**[`dmfdeploy`](https://github.com/dmfdeploy/dmfdeploy) is the front door.** It's +the umbrella repo, with the consolidated knowledge base, the decision record +(ADRs), and cross-repo coordination. The eight `dmf-*` repos are the +components. Each README says what the component does and links back to the +umbrella. ## How this org works -- **One backlog:** [umbrella Issues](https://github.com/dmfdeploy/dmfdeploy/issues), - scheduled on the org board. Component-repo issues are drive-by intake only. -- **Questions / proposals:** [umbrella Discussions](https://github.com/dmfdeploy/dmfdeploy/discussions) - (Q&A, and the RFC-before-ADR pipeline). -- **PRs:** Conventional Commits, DCO sign-off, rebase-merge; CI must be green — - **approval lands the PR automatically**. -- **Corrections:** what the project said in public that turned out wrong, and - what is right, is logged in - [CORRECTIONS](https://github.com/dmfdeploy/dmfdeploy/blob/main/docs/CORRECTIONS.md). -- Much of the platform is built by AI agents under operator orchestration — by - design, documented as method in - [JOURNEY](https://github.com/dmfdeploy/dmfdeploy/blob/main/docs/JOURNEY.md#working-with-agents-the-method). +- **One backlog:** [umbrella Issues](https://github.com/dmfdeploy/dmfdeploy/issues). + A milestone means an issue is scheduled. An issue opened in a component repo + is triaged within about a week: it's closed, or linked to an umbrella issue + where the work continues. +- **Questions and proposals:** [umbrella Discussions](https://github.com/dmfdeploy/dmfdeploy/discussions), + for Q&A, early ideas, and the RFC that comes before a cross-cutting ADR. +- **PRs:** Conventional Commits, DCO sign-off, and rebase merges. **A PR merges + automatically once its required reviews and checks pass**, unless it's a + draft or carries the `hold` label. +- **Corrections:** [CORRECTIONS](https://github.com/dmfdeploy/dmfdeploy/blob/main/docs/CORRECTIONS.md) + logs each public statement that turned out to be wrong, with the correct + version. +- **Built with AI agents:** agents build much of the platform under the + maintainer's direction. That's deliberate, and + [JOURNEY](https://github.com/dmfdeploy/dmfdeploy/blob/main/docs/JOURNEY.md#working-with-agents-the-method) + documents it as a method. Licensed [Apache-2.0](https://github.com/dmfdeploy/dmfdeploy/blob/main/LICENSE).