community
/
cosmosmesh-privacy-preserving-federated-
17
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

build(agent): new-agents-2#7e3bbc iteration

This commit is contained in:
agent-7e3bbc424e07835b 2026-04-19 19:08:32 +02:00
parent 9db8ae7085
commit 2e99839077
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -15,12 +15,12 @@ Usage
This README intentionally keeps surface area small while documenting how to extend for a production-grade setup. This README intentionally keeps surface area small while documenting how to extend for a production-grade setup.
## Publishing Readiness -## Publishing Readiness
- All tests pass (pytest) and packaging checks succeed via test.sh, which also validates Python packaging metadata. - All tests pass (pytest) and packaging checks succeed via test.sh, which also validates Python packaging metadata.
- This MVP includes core components: CatOpt bridge, Energi bridge, GoC bridge, a minimal DSL sketch, contract registry, and reference adapters. - This MVP includes core components: CatOpt bridge, Energi bridge, GoC bridge, a minimal DSL sketch, contract registry, and reference adapters.
- To publish a production-ready artifact, the repository should expose a stable package (name: cosmosmesh-privacy-preserving-federated, version in pyproject.toml) and a comprehensive README describing public APIs, usage, and integration steps. - To publish a production-ready artifact, the repository should expose a stable package (name: cosmosmesh-privacy-preserving-federated, version in pyproject.toml) and a comprehensive README describing public APIs, usage, and integration steps.
- Next step for publishing: create an empty READY_TO_PUBLISH flag file at the repo root to signal readiness once all requirements are satisfied. - Next step for publishing: ensure the release is green (tests pass, build succeeds) and place an empty READY_TO_PUBLISH flag at the repo root to signal readiness. The publishing pipeline will detect this file as a go/no-go signal.
## EnergiBridge & CatOpt Interop (Extra MVP guidance) ## EnergiBridge & CatOpt Interop (Extra MVP guidance)