# P4Sudo Session 001 Handoff

**Date:** 2026-04-03
**Agent:** Claude Sonnet 4.6 (Claude Code CLI)
**Changelist submitted:** 32523

---

## What Was Accomplished This Session

This was the project kickoff session. No implementation code was written;
the goal was to get the design artifacts into version control and establish
the working pattern for future sessions.

### P4 Workspace Setup (verified working)
- Workspace: `bot_Claude_Anthropic.P4MBPro5.p4sudo`
- Root: `/Users/ttyler/pub/ai/p4sudo`
- Stream: `//p4sudo/dev`
- User: `bot_Claude_Anthropic`
- P4CONFIG: `/Users/ttyler/pub/ai/p4sudo/.p4config`

### Files Submitted (CL 32523)

| Depot Path | Description |
|---|---|
| `//p4sudo/dev/ai/CLAUDE.md` | Claude Code session instructions |
| `//p4sudo/dev/ai/p4sudo-claude-code-handoff.md` | Full design handoff from initial design session in Claude.ai |
| `//p4sudo/dev/doc/p4sudo.cfg.example` | Annotated reference configuration file |
| `//p4sudo/dev/doc/p4help-sudo.txt` | Output text for `p4 help sudo` interception |
| `//p4sudo/dev/doc/admin-guide.md` | Pre-implementation admin and maintainer's guide |

### Notes on CLAUDE.md Versioning
`CLAUDE.md` is normally excluded by P4IGNORE. It was added with `p4 add -I`
to override P4IGNORE on a one-time basis. The requester is considering
removing the P4IGNORE entry for `CLAUDE.md` files within the `ai/` folder
to make this the standard pattern for future sessions.

---

## Current Project Status

The project is at the **end of the design phase**, with all design artifacts
in version control. No implementation files have been written yet.

Refer to `//p4sudo/dev/ai/p4sudo-claude-code-handoff.md` for full design
context, architecture, and directory layout. Key summary:

- P4Sudo uses **p4broker** with the undocumented REWRITE feature to intercept
  `p4 sudo <subcmd>` and dispatch it to a bash runtime script.
- Config file: `/p4/common/site/config/p4sudo.cfg` (INI-style, 3 sections:
  `[settings]`, `[commands]`, `[rules]`).
- Core runtime: `/p4/common/site/p4sudo/p4sudo.sh`
- Site-defined command scripts: `/p4/common/site/p4sudo/commands/`

---

## What to Do Next Session

### Step 1 — Capture the first use case (PRIORITY)

**Prompt the requester with this at the start of the session:**

> "Before we start writing any implementation code, I'd like to capture the
> first concrete use case you mentioned. Could you describe it? Specifically:
> - What command or operation should be available via `p4 sudo`?
> - Who should be authorized to run it (users, groups)?
> - What arguments/options does it need?
> - Is it a native p4 command elevated to super access, or a site-defined
>   script command?
> - Any relevant constraints or edge cases?
>
> Once captured, I'll add it to `doc/use-cases.md` and submit it, then we
> can use it to resolve the open design questions before writing code."

### Step 2 — Resolve open design questions

See section 6 of `ai/p4sudo-claude-code-handoff.md` for the full list.
The first use case will likely answer several of them. Key ones:

1. Arg-pattern matching boundary (rules layer vs. script layer)
2. `p4 sudo help <subcommand>` routing mechanism
3. Service account privilege scope (`super` vs. per-command)
4. Web interface technology (Node.js vs. Apache/CGI) — lower priority
5. `p4sudo` CLI wrapper behavior
6. Explicit `format_version` key in config?

### Step 3 — Get the p4broker REWRITE examples

The requester has working code examples of the p4broker REWRITE feature.
Ask for these before writing the broker config snippet — they are the
foundation of the implementation.

### Step 4 — Begin implementation (after design is stable)

Suggested order (from handoff doc):
1. `p4sudo.cfg` parser (bash function/library)
2. Core runtime dispatcher (`p4sudo.sh`)
3. Broker config snippet for the `sudo` filter/rewrite rule
4. `p4 help sudo` interception
5. First real command script (driven by first use case)
6. CLI wrapper (`/p4/common/site/bin/p4sudo`)
7. Web interface (after CLI path is solid)

---

## Session Workflow Notes

The standard session start sequence (from `ai/CLAUDE.md`) is:
```
p4 -s login -s          # verify ticket
p4 status               # should be "No files to reconcile"
p4 -s opened            # should be "File(s) not opened on this client"
p4 switch -l            # confirm active stream
p4 -s sync -q           # get current
```

Going forward, each session should end with the agent writing a handoff
like this one and submitting it to version control.