corp-v1/portal
2
0
Fork 0
Code Issues Pull Requests 2 Actions Packages Projects Releases Wiki Activity

docs: remove AeroSim drawio copy
Build and publish Corp v1 steering documentation / build (push) Successful in 33s
Details

Browse Source
This commit is contained in:
jarvis-at-skic
2026-08-13 13:55:58 +00:00
parent 966adeb1bd
commit d809093885
1 changed files with 3 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/projects/aerosim.md
+3 -7
View File
@@ -82,16 +82,13 @@ All use default branch `test` and are primary for AeroSim work:
- `development-scripts--aerosim` - `development-scripts--aerosim`
- `devsecops-ci-cd-gitea--aerosim` - `devsecops-ci-cd-gitea--aerosim`
- `documentation-docusaurus--aerosim` - `documentation-docusaurus--aerosim`
- `drawio-main--aerosim`
- `template-engine-copier--aerosim` - `template-engine-copier--aerosim`
- `corp-v1-channel-general--aerosim` - `corp-v1-channel-general--aerosim`
- `corp-v1-channel-architecture--aerosim` - `corp-v1-channel-architecture--aerosim`
- `corp-v1-channel-delivery--aerosim` - `corp-v1-channel-delivery--aerosim`
- `corp-v1-channel-releases--aerosim` - `corp-v1-channel-releases--aerosim`
Each repository records the central source branch and commit in `ADOPTION.md`. Each repository records the central source branch and commit in `ADOPTION.md`. Architecture and documentation work reference the global [`drawio-main`](https://gitea.lego-cloud.eu/home-v1-skills-code-agent/drawio-main) skill.
Current steering policy defaults to seven adopted engineering skills plus four channel skills and references global `drawio-main`. AeroSim retains the historical `drawio-main--aerosim` repository pending an explicit team decision to retain it as an approved exception or retire it; no repository was deleted during alignment.
## Verification ## Verification
@@ -101,12 +98,11 @@ Current steering policy defaults to seven adopted engineering skills plus four c
- Application tests: four passed across web, API, and shared flight core. - Application tests: four passed across web, API, and shared flight core.
- Application and documentation production builds: passed. - Application and documentation production builds: passed.
- Project-team access to both project repositories: verified. - Project-team access to both project repositories: verified.
- Skills-team organization contains all twelve adopted skill repositories on default branch `test`: verified. - Skills-team organization contains all eleven adopted skill repositories on default branch `test`: verified.
- Harbor organization variable names and secret name `HL_V1_HARBOR_ROBOT_GITEA_ACTIONS_V1_SECRET`: verified without reading secret values. - Harbor organization variable names and secret name `HL_V1_HARBOR_ROBOT_GITEA_ACTIONS_V1_SECRET`: verified without reading secret values.
- Product lifecycle, solution traceability, and release-readiness registries now exist in project documentation. No Epic or Feature was assigned human approval retrospectively. - Product lifecycle, solution traceability, and release-readiness registries now exist in project documentation. No Epic or Feature was assigned human approval retrospectively.
- Both application and documentation `test` branches currently have no branch-protection rule. - Both application and documentation `test` branches currently have no branch-protection rule.
## Outstanding governance decisions ## Outstanding governance decisions
1. A human team member must decide whether to retain `drawio-main--aerosim` as an explicitly approved project copy or use only global `drawio-main` and retire the copy through the normal reviewed process. A human team member must approve the desired branch-protection policy for both project `test` branches before protection is configured. No protection was added autonomously because required approvals and merge semantics are a governance decision.
2. A human team member must approve the desired branch-protection policy for both project `test` branches before protection is configured. No protection was added autonomously because required approvals and merge semantics are a governance decision.