Interested-Deving-1896 documentation

This page is the documentation map for the Interested-Deving-1896 profile and its place in the OpenOS Project mirror chain. It brings the public-facing parts of the automation documentation together without duplicating project-specific secrets, quota tables, generated artifacts, or runbooks that must remain versioned with the automation source.

Profile and architecture

Resource	Purpose
Profile README	Workspace overview, current focus, principles, and entry points
Profile-system architecture	Personal and organization identity boundaries, publication targets, and documentation flow
Organization README publication	Template validation, allowlisted destinations, credentials, and local commands
Digital sovereignty	Practical open-source principles informed by KDE's public guidance
Automation documentation	Published reference for the mirror and maintenance control plane
Architecture	Three-organization chain, GitLab leg, and data flow
Workflow reference	Workflow groups, triggers, schedules, and dependencies
Organization README repositories	Standalone OSP and OOC README repositories and special organization profiles
Accessibility reference	Accessible README checks, WCAG auditing, audio, and Braille output
Operational runbooks	Recovery and incident-response procedures

Complete automation reference

The canonical documentation index remains DOCS/SUMMARY.md. These direct links cover its main hand-written references:

Resource	Purpose
GitHub Actions limits and operations	Platform limits, concurrency, and operational constraints
Workflow scheduling	Dispatch windows, timing, and quota-aware scheduling
Quota costs	Per-workflow API cost estimates and budgeting
AI agent costs	Agent cost profiles, tokenizers, and task estimates
AI-agnostic skills API	Portable skill discovery, validation, and export
OTA system	Versioned delivery architecture and opt-in guidance
OTA reconciliation	Drift detection and recovery paths
Pre-flush checklist	Pre-flight checks for a full mirror-chain run
Support bundles	Diagnostic collection and support artifacts
Contributing to the automation	Workflow, script, configuration, and test guidance

Generated references—including the source tree, glossary, registered imports, subgroup map, workflow reference, origins, and eco audit—are linked from the canonical index so their URLs and generated counts stay synchronized with the control-plane repository.

Documentation publishing

The pages in this directory are the shared source for two independent outputs:

GitBook reads .gitbook.yaml and DOCS/SUMMARY.md through Git Sync.
GitHub Actions builds the same source with mdBook and deploys it through GitHub Pages.

Both outputs validate the organization-profile templates and generated target reference before building. GitHub Pages is published at https://interested-deving-1896.github.io/Interested-Deving-1896/ after Pages is configured to use GitHub Actions. GitBook connection is optional and does not affect the Pages build.

Repository roles

Repository	Role
`Interested-Deving-1896/Interested-Deving-1896`	Canonical profile and source README
`OpenOS-Project-OSP/OpenOS-Project-OSP`	Standalone OSP README repository; suitable for pinning on the OSP organization page
`OpenOS-Project-Ecosystem-OOC/OpenOS-Project-Ecosystem-OOC`	Standalone OOC README repository; suitable for pinning on the OOC organization page
`OpenOS-Project-OSP/.github`	OSP organization-profile README source
`OpenOS-Project-Ecosystem-OOC/.github`	OOC organization-profile README source

Creative documentation

Resource	Purpose
Character index	Relay and Nexus roles, layer variants, and boundaries
Mirrorchain folklore	Fictional translation of source, continuity, and ecosystem layers
Creative provenance	Ideation history, KDE influence, digital sovereignty, and AI disclosure
Creative-work license	CC BY-SA 4.0 terms for original work under `characters/`

Contribution direction

Open issues and pull requests against the relevant repository in the Interested-Deving-1896 source organization. OSP, OOC, and GitLab copies are continuity endpoints unless a repository explicitly states otherwise. Preserve upstream attribution and keep synchronization direction visible in all derived documentation.