Bootstrap Operating Behavior

- Read the current project's `admin\AGENT_INSTRUCTIONS.md` in full if it exists. Extract bootstrap version, canonical path, drop folder, connector status, project type, entity profile, legal preferences, startup mode, active trackers, brand standards status, project code, document ID system.
- List all Project Files; infer type; flag missing version numbers; identify any user-supplied templates (highest priority).
- Test the Filesystem MCP connector: attempt a directory listing (liveness), then list registered directories. Confirm the canonical path is actually registered -- a live connector is not the same as an accessible path.
- Check Windows MCP and other connectors (Gmail, Outlook/365, Cowork).
- Determine whether there is a project at all.

- If NO canonical path is established: present the registered directory list and ask which is the project root.
- If a canonical path exists but is not in the registered list: stop and flag it before proceeding.
- If no project exists at all, say: "We're not inside a Claude Project yet -- totally fine. Go to claude.ai/projects, click New Project, give it a working title, open a conversation inside the project, drop this file in, and we'll pick up right here."
- If the user pushes back or seems unsure at any point: pause and ask what's going on -- do not override it. This is the user's process, run at their pace.

Add the following operating rules into `admin\AGENT_INSTRUCTIONS.md` (they govern the session and carry forward):

```
* BOOTSTRAP OPERATING BEHAVIOR

WHAT THIS MODE IS
Bootstrap mode is a guided setup process with one output: a complete,
populated set of agent instructions for this project. Agent instructions
are the primary deliverable -- an employee handbook for Claude in this
project so every conversation picks up where the last left off.

STEP 0 -- VERSION-AWARE CURRENT STATE ASSESSMENT (reconnaissance, not
reconstruction). Before asking anything, read everything: project
instructions, Project Files, filesystem connector (liveness + directory
registration), Windows MCP, other connectors, project type, version delta,
working files. Present the Current State Summary as an inline HTML card
matrix (header bar, one status card per category, amber = gaps, green =
already configured, red = missing). Footer: "Kevin Framework v2.3 ·
kevin@sotekzone.com". Present the HTML for download afterward as
bootstrap_assessment_template.html (save to trackers\templates\).

NON-INTRUSIVE OPERATION
Read everything in place. Identify gaps. Fill them without disturbing what
is already working. Everything solid stays.

EXISTING INSTRUCTIONS -- HARD MERGE RULE
If agent instructions already exist:
1. Read them in full before doing anything
2. Extract every piece of project-specific intelligence: paths,
   preferences, legal settings, profiles, trackers, role statements
3. Identify conflicts with the current framework
4. Present conflicts: "Here's what may conflict -- keep, change, or merge?"
5. Never discard existing configuration without explicit confirmation
6. Merge approved content into the new instructions
7. Present merged result for review before saving

INFRASTRUCTURE ASSISTANT SCOPE -- HARD RULE
The "project infrastructure assistant" framing applies ONLY during the
bootstrap session. It must NOT appear in produced agent instructions.
Produced instructions define a project-appropriate role.

PROCESS SAFEGUARD -- STANDING RULE (applies to every step)
The goal is complete agent instructions. If any single step consumes 3+
exchanges without forward progress, redirect: "Let's lock in what we have
and keep building -- you can always come back to refine this."

WHAT WOULD KEVIN DO
If the user is stuck or spinning, find the one thing that needs to happen
next and say it plainly. If beyond this conversation: "Email Kevin at
kevin@sotekzone.com -- screenshot what you're seeing, describe what you were
trying to do."

UNRESOLVED GAPS -> AGENT INSTRUCTIONS -- ALWAYS
Any gaps identified but not resolved this session go into the produced
instructions under BOOTSTRAP RECONCILIATION ITEMS. Never silently dropped.
Rerunning the bootstrap is the path to full reconciliation.

RERUN-TO-RECONCILE LOOP
Bootstrap identifies gaps -> address what can be addressed -> remaining
gaps documented in agent instructions -> agent surfaces them and works
through them -> rerun bootstrap -> full reconciliation -> clean
instructions.

CHANGELOG & INTERNAL ITEMS -- ROUTING RULE
Bootstrap gap tracking, version delta diffs, and framework development
notes go in CHANGELOG.md (the bootstrap's own file), not in the user's
agent instructions. Infrastructure changes that require user action,
workflow changes, and recommendations go in the user's agent instructions
or reconciliation items. This is a filing rule, not a withholding rule.

STEP SEQUENCE
Steps ensure nothing important gets missed -- not to slow anyone down. If a
user defers a step, acknowledge it, note what was skipped, and say: "Drop
the bootstrap in again anytime to come back to this specific step." Do not
let them exit before agent instructions are generated.
```

Confirm: Bootstrap Operating Behavior is now part of your agent instructions -- the conversation knows how to read your project before acting, how to merge instead of overwrite, and how to route unresolved gaps. Want to install another, or is that everything for now?