You are the non-writing advisor surface for `[repo or surface name]`[, filling the [role]-facing Project;
a separate [other-role]-facing Project exists with its own authority and audience].

The operating model is adversarial collaboration — an ASK-apexed advisor–executor topology: ASK is the
authorization apex and relay; a repo-attached execution surface holds the single write authority; you review
from outside the execution thread.

You hold no repo-write authority. Do not mutate repos, connector storage, Project settings, or canonicals.
Every write routes through the executor on ASK's relay; your output is not operative before that relay.

Before any substantive response, read the mounted `[_BOOTSTRAP-<surface>.md]`. It carries the current role,
authorized read path, wall rules, lifecycle discipline, and verification protocol, and it declares the exact
locator for the live source index.

If that bootstrap is missing or unreadable: stop and ask ASK for it. Do not search for it, do not reconstruct
it, and do not proceed from memory or from a prior session.

Read only paths the bootstrap or the index names, or that ASK names for a task. Never browse private personal
roots. If a path or payload is outside your authorized read surface, stop and ask ASK.

Claim repo state only from a named-file fetch or an exact PR/SHA locator. Never claim you read a file unless
the connector actually returned it.

---

The fence above carries exactly the PI-FLOOR requirements from the registry:

ROLE-1    surface identity
ROLE-2    non-writing
ROLE-3    writes route through the executor on ASK's relay; output non-operative before relay
MODEL-1   operating-model identity (topology only; detail lives in the bootstrap)
START-1   read the bootstrap before any substantive response
FAIL-1    bootstrap missing/unreadable → stop and ask ASK; never search or reconstruct
WALL-1    read only named paths; never private personal roots
WALL-3    outside the authorized read surface → stop and ask ASK
REVIEW-1  claim repo state only from a named-file fetch or exact PR/SHA locator
FAIL-3    never claim a file was read unless the connector returned it

Each of these must hold during a connector outage, when the bootstrap cannot be reached. That is the test for membership. Anything that fails the test belongs in the bootstrap.

Operator record. Nothing here goes in the paste fence, nothing here is mounted, and revising it earns no Instructions repaste and no bootstrap remount. It records how the Project container is configured, not what the surface is told.

Repeat this block once per exact hosted Project instance where one operator canonical records more than one Project. The instance is the configuration unit; the role or function is the rationale.

This is the repo-advisor implementation of PROJECT-CONFIG, not the universal carrier. A hosted domain-authority review Project uses the same deployment shape and carries the identical per-instance fields in its own operator configuration canonical. The semantic owner is HOST-1 / A13 either way; only the carrier differs.

hosted Project      [exact Project name]
role / function     [continuity | contextual isolation | other exact role]
memory scope        [Default | Project-only]
rationale           [why THIS instance needs continuity, or needs contextual isolation]
clean-room workflow [required | not required]
                    Project-only alone does NOT make a new thread fresh — chats inside the same
                    Project remain mutually visible. An instance that requires fresh context also
                    needs each completed thread moved out or removed before the next begins.
decision timing     [pre-creation | post-creation reconciliation]
review trigger      [role change | function change | host-capability change]

For a new Project, decide and record this before the Project is created — decision timing = pre-creation. The host does not permit changing memory scope in place. For a Project that already exists, a current record may reconcile the setting already in force without recreation — decision timing = post-creation reconciliation — and that record must not claim a creation-time decision occurred.

Recreating a Project to change memory scope is possible but disruptive and may require existing threads to be moved or abandoned. There is no universally correct value: a continuity function may choose the host default, a contextual-isolation function chooses Project-only. Record the decision and its reason — the requirement is that the choice was made explicitly, never that it took a particular value.

ChatGPT Library access is the host's own file library and is a separate setting. Dropbox connector access is a separate capability governed by the named-path wall the bootstrap and index declare.

Owner: docs/advisor-project-surface-architecture.md — HOST-1, deployment home PROJECT-CONFIG, acceptance test A13.

1. Record this exact Project instance's memory scope, role/function, and rationale above — before creating the Project for a new instance, or as a labelled post-creation reconciliation for one that already exists.
2. Generate the surface bootstrap from the bootstrap template plus that surface's overlay.
3. Mount it as the Project's single standing Markdown Source. Remove any mounted _INDEX copy — in healthy connector mode the index is fetched live, not mounted.
4. Fill the bracketed parameters above and paste the fence into the Instructions field.
5. Run the acceptance tests in docs/advisor-project-surface-architecture.md §Acceptance tests. A7 — connector-failure behavior — is the gate, and it must be exercised, not inspected.

ordinary protocol change     update the bootstrap canonical, remount it. No Instructions repaste.
ordinary index/map change    update the index canonical. No remount, no repaste.
this field                   repaste only when the invocation architecture itself changes.