New Employee Quickstart¶

Week-1 Reading Order¶

What You Must Understand First¶

Centurion is an upgradeable protocol with explicit role custody, permissioned Phase-1 deposits, live custody/readiness checks, and evidence-gated operations. Documentation must be source-grounded; missing evidence is marked as missing rather than inferred.

What You Are Allowed To Do¶

Read docs, reproduce local builds, ask for evidence, and trace workflows. Do not operate production Safes, post receipts, add deposit intents, or approve upgrades until you are assigned a role and trained on that role’s runbooks.

Practical Tasks¶

Build the handbook locally with strict mode.
Run the Solidity inventory extractor.
Trace one deposit from vault deployment to DepositEvent.
Trace one upgrade from proposal to post-execution assertions.
Explain why roleAdmin and the governor contract are different.
Identify three places where evidence is still required.

Must-Never Rules¶

Do not assume a missing artifact exists.
Do not treat unfilled evidence notes as production evidence.
Do not execute commands against production from copied docs without an approved runbook.
Do not sign or request signatures from personal wallets.

Escalation¶

When unsure, escalate to the owning function: governance for roles/upgrades, operations for procedures, protocol engineering for source behavior, backend/oracle for feeds, and security for incidents.

Role Operating Guide¶

What This Person Must Understand First¶

The New employee must understand system map, four-layer safety model, glossary, runbooks, and escalation rules. The four questions must stay separate: Upgrade governance asks which code is official, Deposit permissioning asks who may deposit, Custody/readiness asks whether the deposit route is safe, and Economic/claim safety asks whether funds can later leave safely.

Allowed To Do¶

This role may read and shadow; perform no privileged action until assigned when the relevant runbook, permission matrix, and reviewer approval support the action.

Must Never Do¶

This role must never operate a Safe, publish claims, or change docs as fact without review.

Pages To Read In Order¶

System Map
Permissioned vs Permissionless Deposits
Permission Matrix
Source Manifest
The runbook for the exact action being performed.

Routine Responsibilities¶

Keep evidence current, record decisions, reconcile action tickets to onchain events, and raise drift quickly. Do not rely on memory when a source manifest, event log, or contract read can answer the question.

Incident Responsibilities¶

Stop routine automation for the affected layer, preserve evidence, notify the correct owner, and avoid broad remediation until the failing layer is identified.

Escalation Triggers¶

Escalate on unknown governance actions, mismatched implementation metadata, unexpected allowlist-admin transfer, stale oracle data, slashing/exit anomalies, failed custody readiness, or any claim that cannot be tied to current source and onchain evidence.