MyRepo · Cityscape Enterprises LLC
Security boundaries
MyRepo is in development; these are the product boundaries, and the offline demo demonstrates the deterministic state model rather than a connected production workspace.
Facts before advice
No language model decides a state: pure reducers derive stages, signals and wait reasons from repository facts, with shared fixtures checking the rules.
Credentials stay server-side
The V1 integration contract keeps GitHub installation tokens server-side by minting them on the server and redacting stored payloads and logs; connected-runtime proof is still required, and the separate credential vault uses explicit audited grants.
Workspace isolation
The V1 workspace contract requires membership and row-level isolation for every read, with a two-tenant test required before claiming a connected deployment prevents cross-workspace access.
No auto-merge
MyRepo has no auto-merge: it shows eligibility and evidence, while any guarded action must honor the repository’s required checks and the workspace’s explicit authorization.
No leaderboard
There is no leaderboard: the product presents repository work and release evidence without per-person rankings.
Data and retention
What is stored and for how long comes from the generated data inventory: read the privacy and retention notice.
Report a concern to support@myagency.dev; do not include a token, password or private repository content.