Senior core: junior mirrors & merge to mainstream
career_level=senior (any role): exclusive junior mirror desk at /businessite/core/mirrors, merge queue (gate only). SLUG + own sandbox still apply. Analysts: no git clones. my mirrors · merge queue · guide senior-core.
Chat commands
guide senior-core · my mirrors · open mirror <slug> · merge queue · request merge <slug> · approve merge CODE · /businessite/core/mirrors
Senior core team onboarding
Senior means career_level = senior on your core team member record
(Architect, Analyst, Admin, or Developer on any of Data / System / User / Security / App).
Seniors still get a personal SLUG, cloud mirror, and localhost bootstrap — the same slug process as juniors — plus exclusive access to every junior’s mirror for review and facilitating merges into mainstream.
Appoint / promote
- Applications: Appoint senior (vs Appoint junior)
- Existing members: team member form → Mark senior
- Grants group
BusinesSite Senior Mirror Reviewer(re-login)
Exclusive junior mirrors
Portal: /businessite/core/mirrors
Juniors (intern / junior) cannot list peers. Mid stays private in MVP.
my mirrors open mirror SLUG request merge SLUG summary… merge queue approve merge MR… reject merge MR…
Merge to mainstream (gate only)
- Review junior work in their
cloud-dev-{{slug}}mirror / DB - Submit or approve a merge request
- Approve writes a JSON gate under
uat_gate/merge_to_mainstream/— no auto git push - Senior/System Architect runs the deliberate merge to
cloud-dev/master
Git vs mirrors by role
| Role | Own SLUG mirror | Junior mirrors | Git clone URLs |
|---|---|---|---|
| Senior Developer / Architect / Admin | Yes | Yes (exclusive) | Yes (scm help) |
| Senior Analyst | Yes | Yes (exclusive) | No |
| Junior any role | Yes | No | Dev/Arch/Admin only |
Related
- guide developer-git · guide core-team
- Backend: BusinesSite Core → Merge reviews
Leave any multi-step flow: say
stop or cancel.
Say continue to stay.