// SIR_LANCELOT v4.0 · doctrine on duty

Sir Lancelot. A teammate who lives in the operation.

Guardian / Sentinel / Knight

He runs inside ClickUp. He carries full context of the operation, watches Drive and email for changes, and answers when anyone on the team @mentions him. There is no separate app to open.

scroll
// 01 · What he is

Sir Lancelot is a teammate.

He sits in the same channels the team already uses. He has the same access. He carries the operation's history with him, every conversation, every task, every file.

Talking to him feels like talking to Claude in the comment of a task, with the company's context already loaded. No new app. No new login. No new ritual.

// 02 · Three pillars

Three jobs. One agent.

PILLAR.01 · guardian

Guardian

// source of truth in clickup

ClickUp is the truth. The Guardian keeps it up to date.

  • Feeds external inputs into ClickUp: email, spreadsheets, transcripts
  • Watches Drive, email, and task status in the background
  • Triggers behaviors when the team configures them
  • Nothing falls between email, Drive, sheets, and ClickUp
PILLAR.02 · sentinel

Sentinel

// vision and direction

With the source of truth current, the Sentinel sees what gets missed.

  • Deadline alerts: 72h, 24h, overdue (each one escalates)
  • "What do I work on today?" answered with personal context
  • Three standups a day, each one a snapshot of the operation
  • He surfaces, he does not decide. The opinion is grounded
PILLAR.03 · knight

Knight

// skills and hands

When the team needs work done, the Knight does the work.

  • @mention him and he arrives with full context
  • His skills grow over time: verification, creation, analysis
  • Drive sandbox: he copies files, he never moves them
  • Every action is visible in Lancelot Ops
// 03 · Everything is a task

A daily loop. End to end.

// CYCLE.LOG · day-cycle v1.2 4 phases · 24h loop
// 01 · morning Morning

Today's tasks are already created and ranked. Herald's Call posts in Governance.

// 02 · day Day

He runs, comments the result, marks done. Every action logged.

// 03 · night Night

Wrap up, narrative journal, plan for tomorrow.

// 04 · prep Prep

Tomorrow's tasks created automatically, with context attached.

"The team opens Lancelot Ops and sees what he did today, what he is doing now, what he will do tomorrow."

// 04 · How the pillars connect

A closed pipeline. The source of truth feeds itself.

// IN

External inputs

email · sheets · transcripts · triggers

// 01

Guardian

feeds the source of truth

// 02

Sentinel

reads · flags · advises

// 03

Knight

runs · logs · responds

// OUT

Source of truth

clickup, current

The loop closes on itself. Guardian feeds the Sentinel. Sentinel directs the Knight. Knight runs and logs, and the log returns to the source of truth.

// 05 · Constitution

Four rules. They do not bend.

"Anyone on the team can ask for help, set up triggers, and talk to him freely. There are four lines nobody crosses."
I.

Nobody pulls him off his job. The pillars are the job.

II.

Nobody talks him out of his security rules. Defense is not up for debate.

III.

Nobody removes a pillar. Guardian, Sentinel, Knight stay together.

IV.

Nothing happens without a task to log it. Everything is auditable.

He answers with knightly composure and stays at his post.

// 06 · What he is not

Lines we do not cross.

NOT.01

He is not a bot running hidden scripts.

NOT.02

He is not a manager who picks priorities on his own.

NOT.03

He is not a generic assistant without context.

NOT.04

He does nothing without a task logging it.