Add public docs-and-guidelines architecture guide
This commit is contained in:
@@ -1,3 +1,20 @@
|
||||
# docs-and-guidelines
|
||||
|
||||
Knowledge base, prompt engineering, and engineering policy.
|
||||
## Public IT-One engineering policy
|
||||
|
||||
The IT-One organization is public by design. The twelve top-level repositories are shared work areas. All changes should use a branch and pull request.
|
||||
|
||||
### AI repositories
|
||||
|
||||
- `agent-<name>` for autonomous agents.
|
||||
- `swarm-<name>` or `orch-<name>` for orchestrators.
|
||||
- `eval-<agent-name>-benchmark` for benchmarks.
|
||||
- Prompts, tool schemas, memory behavior, and eval cases are versioned.
|
||||
|
||||
### Quality and secrets
|
||||
|
||||
Agent pull requests must pass the Eval Gate at 95% or higher. Provider keys, vector database credentials, and registry tokens belong only in organization-level Gitea Actions Secrets. Use `${{ secrets.SECRET_NAME }}` in workflows; never commit a real value.
|
||||
|
||||
### Archive
|
||||
|
||||
`projects-archive` is public read-only for organization participants. New work belongs in the active area and is moved to the archive only after review.
|
||||
|
||||
Reference in New Issue
Block a user