Trailhead Documentation

Current product status

How the parts of Trailhead connect

See what works today, what is connected, and what still needs to be finished before Trailhead is ready for field use.

Core operating loop + Supporting product areas

Direct connectionIndirect connection

81%

Roadmap progress

81%

Roadmap progress

Ready 100 · Works but needs testing 75 · Partial 50 · Planned 0; weighted by what works, how connected it is, and field readiness

Direct connectionIndirect connection

Core operating loop

Supporting product areas

Progress based on the roadmap

CIS

The trip record that brings together clients, travel, fishing days, and overall progress.

90%

How this percentage is calculated

What works100%

How connected100%

Ready for field use50%

What works today

A CIS can be created and managed with clients, travel details, and handoffs.
CIS creates Programs from known trip context and shows linked reports, lifecycle health, and the exact work blocking closure.
Client activation, pre-trip information, trip timeline, and feedback are partly built.

What remains

Rerun the complete management flow in staging against the fixed Alpha 1 candidate.
Finish the client journey: activation, trip closure, post-trip recap, and useful context for returning clients.

Connected with

Programs · creates each fishing dayReview & Closure · updates trip progress

Sources reviewed

CIS Roadmap · Current StateTrailhead Alpha 1 · Core Product Requirements 1, 3, and 4CIS Roadmap · Current State / Must-Fix Gaps

Delivery ownership

Who leads each part of the roadmap

This roadmap shows who leads product delivery and how each lane contributes to Alpha 1. Operating responsibilities inside Trailhead remain defined by the Playbook scenarios.

Alpha 1 candidate focus

The core lifecycle is implemented. Alpha 1 remains in preparation until one fixed candidate closes the staging, device, connectivity, observability, and release-evidence gates.

Implemented baseline

CIS → Program → execution → linked Fishing Report → closure
Exact blocker links, role and lodge boundaries, and repeatable seed/reset
Agreement calculations, access-season Finance status, settlement paths, and financial trace implemented
GPS traceability, recovery, and mobile/web live-map path exercised
Shared Field Knowledge Passports, multi-guide reconciliation, and Weekly Meals planning and spreadsheet handoff implemented
Approved Trailhead role catalog implemented in shadow mode with reconciled staging assignments

Open before go/no-go

Freeze one candidate and rerun the golden path in staging
Consolidate the exercised GPS path with the full phone-data/Starlink fixed-candidate certification matrix
Validate access Finance filters, Owner balance cadence alerts, Guide pays at access reminders, activity evidence, and the SettleWise settlement handoff
Complete canonical role cutover and surface-parity checks; shadow assignments do not yet replace legacy authorization
Complete the live Sentry review, release notes, support owner, and rollback record

Tomi

Inventory & Mobile App

Keep physical gear trustworthy and make Trailhead reliable for people working in the field.

Owns

Inventory and gear workflows
Mobile platform, navigation, offline behavior, and releases
Mobile integration of other product capabilities
Guide field execution

Boundary

Tomi delivers CIS, Reports, and Field Knowledge on mobile, but their capability leads define the business behavior and source records.

Alpha 1

Core guide workflow on iPhone: Program, execution, access, and report
GPS traceability and recovery implemented; complete connectivity and candidate-build certification

After Alpha 1

Gear requests, custody, replacements, returns, and Seasonal Kit depth
Mobile integrations owned by the other capability leads

Later

Offline resilience and release readiness

Tincho

Reports

Turn operational records into trusted answers that managers and clients can act on.

Owns

Report definitions, metrics, and data contracts
Report filters, review states, drilldowns, and exports
Reporting experiences across product scopes

Boundary

Tincho owns how source records become reports. The capability that creates each source record remains responsible for its accuracy and workflow.

Alpha 1

Directly linked Fishing Report submission and closure evidence
Traceable access-charge and settlement reporting for the pilot

After Alpha 1

Management report catalog, traceable detail, and exports

Later

Cross-season comparisons and decision-support analytics

Mari

CIS

Make every client trip a trusted operational record from booking through closure.

Owns

Trip, passenger, lodge, service, and travel context
CIS creation, editing, requirements, and handoffs
CIS-level readiness and lifecycle rollups

Boundary

CIS creates the trip envelope and required work. It does not own Program execution, report logic, inventory custody, or curated Field Knowledge.

Alpha 1

A complete CIS that creates Programs from known trip context
Lifecycle health, missing-work reasons, and exact closure links

After Alpha 1

Travel handoffs and operational rollups

Later

Client-facing readiness, timeline, and recap

Benja

Field Knowledge

Turn lodge experience and field outcomes into better future fishing decisions.

Owns

Beat Passports, seasonal context, pressure, and hazards
FIE Quality, Context Quality, and Signals logic
The learning loop from reports and outcomes

Boundary

Field Knowledge curates decision context. It consumes CIS, Program, and report evidence without becoming their source of truth.

Alpha 1

Benja reviews the current Beat Passports and form gaps; Field Knowledge remains outside the Alpha 1 release gate

After Alpha 1

Modify the Beat Passport form from Benja's review, then continue populating passports

Later

Closed-loop recommendations informed by field outcomes

Tomi & Benja

Accesses & Beats

Keep Accesses, Beats, and their agreements operationally ready before Programs depend on them.

Owns

Tomi: Access and Beat records, relationships, logistics, and rules
Benja: Agreement review and clearance
Operational readiness across agreements, Accesses, and Beats

Boundary

Benja reviews and clears agreements in this lane. Beat tactics and curated field context remain in Field Knowledge; Programs and Reports only consume the ready records.

Alpha 1

Populated pilot Access and Beat records with active dated agreements and fee rules
Agreement charges, agreement-owned Owner balance cadence, Finance alerts, Guide pays at access reminders, and access budget control implemented; field validation remains

After Alpha 1

Broader agreement review, clearance, and operational logistics

Later

Usage and outcome feedback that improves future decisions

Tincho & Mari

Guides, Accounts & Payments

Keep guide readiness and financial activity connected, traceable, and explainable.

Owns

Shared ownership of Guides, accounts, and payments
Guide readiness and account visibility
Traceable payment and account movements

Boundary

Tincho and Mari share this lane. Reports remain in Tincho's reporting lane, CIS remains in Mari's CIS lane, and guide field execution remains with Tomi.

Alpha 1

Passwordless guide activation with role and lodge boundaries
Traceable guide earnings and account visibility for the pilot lifecycle

After Alpha 1

Full payment flows, gear-account links, expenses, advances, and reconciliation

Later

Explainable season closure and financial history

When scopes meet on mobile

The capability lead defines the behavior and source of truth. Tomi owns how that capability is integrated and delivered in the mobile app.

Work	Capability lead	Mobile delivery
Reports in the mobile app	Tincho	Tomi
CIS experiences in the mobile app	Mari	Tomi
Signals and Field Knowledge on mobile	Benja	Tomi
Inventory and gear on mobile	Tomi	Tomi

Shared or unassigned ownership

These areas sit outside the four confirmed lanes and need an explicit lead before delivery commitments are made.

Fishing Program definition and readiness
Operations, live oversight, and blocker resolution
Cross-scope integration and final QA

Management reports

High-level reports for management questions that cannot be answered inside one operating scope.

These reports combine trusted signals; they do not move ownership. Every exception must lead back to the source scope that can explain or correct it.

MR-01First to build
Beds & access usage
How does lodge occupancy translate into planned and actual access demand each day?
Management decision
See whether fishing demand is supported by real access usage and investigate guests or crossings that do not reconcile.
For
General and operations managers
Cadence
Daily and weekly
Source scopes
- Trips & CIS
- Fishing Operations
- Accesses & Landowners
See the report→
MR-02Planned
Daily operating health
Are today's and tomorrow's trips ready, in motion, blocked, or waiting for review?
Management decision
Prioritize the blockers that put delivery at risk and open the exact source record behind each one.
For
Operations managers
Cadence
Live and daily
Source scopes
- Trips & CIS
- Guides & Assignments
- Travel & Handoffs
- Fishing Operations
- Operations & Readiness
- Inventory & Gear
MR-03Planned
Trip delivery and outcomes
Did the client promise become completed work with trusted reports and outcomes?
Management decision
Identify incomplete delivery, missing evidence, and recurring gaps before they become service problems.
For
General and operations managers
Cadence
Per trip and weekly
Source scopes
- Trips & CIS
- Clients & Guest Experience
- Fishing Operations
- Operations & Readiness
MR-04Planned
Financial exposure
Which trip obligations, owner charges, and company funds still need explanation or settlement?
Management decision
Review material exposure and follow every amount back to the operating event and financial owner.
For
General management and Accounts
Cadence
Weekly and monthly
Source scopes
- Trips & CIS
- Accesses & Landowners
- Guide Accounts & Payments
MR-05Planned
Open exceptions
Which cross-scope problems still lack a clear owner, next action, or trusted closure?
Management decision
Assign one source owner and one follow-up path for every material exception.
For
Operations leads
Cadence
Live and daily
Source scopes
- Trips & CIS
- Guides & Assignments
- Travel & Handoffs
- Fishing Operations
- Guide Accounts & Payments
- Operations & Readiness
MR-06Available
Client demographics and retention
Who are our clients, and which groups return for another trip?
Management decision
Compare demographic cohorts and returning-client behavior without duplicating canonical client identities.
For
General management and Sales
Cadence
Monthly and seasonal
Source scopes
- Clients & Guest Experience
- Trips & CIS
MR-07Available
Equipment stock coverage
Does current equipment stock cover the sizes and needs recorded for upcoming clients?
Management decision
Identify equipment shortages early and prioritize purchasing or transfers using client demand.
For
Operations and inventory managers
Cadence
Weekly and before each trip
Source scopes
- Clients & Guest Experience
- Trips & CIS
- Inventory & Gear
MR-08Available
Nationality and market mix
Which nationalities and markets make up the current client base?
Management decision
Use trusted client identity data to inform market coverage and communication planning.
For
General management and Sales
Cadence
Monthly and seasonal
Source scopes
- Clients & Guest Experience
MR-09Available
New and returning clients by age
How do new and returning client groups differ by age range?
Management decision
Compare acquisition and retention patterns while keeping unknown birth dates visible.
For
General management and Sales
Cadence
Monthly and seasonal
Source scopes
- Clients & Guest Experience
- Trips & CIS
MR-10Available
Clients by state and city
Where are clients concentrated by state, province, and city?
Management decision
Find geographic concentrations for market planning without inventing locations from incomplete addresses.
For
General management and Sales
Cadence
Monthly and seasonal
Source scopes
- Clients & Guest Experience
MR-11Available
Client data quality
Which client records are incomplete, duplicated, or missing the fields needed for safe operations and reporting?
Management decision
Prioritize identity cleanup and missing-data follow-up before unreliable records affect trips or analysis.
For
Operations, Sales, and data owners
Cadence
Weekly
Source scopes
- Clients & Guest Experience
- Trips & CIS

Trailhead

Alerts & responsibilities

Trailhead defines the source condition, responsible role or daily duty, and escalation. El Encuentro confirms the named primary and backup who cover each responsibility.

23 alerts

A name in this matrix documents operating coverage; it does not grant application access. Unconfirmed assignments remain open for El Encuentro review.

Operational alert responsibility matrix
Alert	When	Source scope	Trigger summary	Responsibility	El Encuentro coverage	Status
Required Program missing	Prepare	Fishing Operations	Required work still has no Program after the preparation trigger.	Primary: Daily Guide Coordinator dutyEscalation: Head Guide	Primary: Dynamic from lodge/day dutyBackup: To confirm	Needs Review
Program needs changes	Prepare	Fishing Operations	A Program has a blocking conflict or requested correction.	Primary: Daily Guide Coordinator duty for routine conflictsEscalation: Head Guide for escalated conflicts	Primary: Dynamic from lodge/day dutyBackup: To confirm	Needs Review
Program data is invalid	Prepare	Fishing Operations	Stored Program data violates the approved Program classification.	Primary: OperationsEscalation: Head Guide when a fishing decision is required	Primary: To confirmBackup: To confirm	Needs Review
Client readiness is overdue	Prepare	Trips & CIS / Client Experience	Required activation or client preparation remains incomplete after its deadline.	Primary: OperationsEscalation: Executive when the client promise is at risk	Primary: To confirmBackup: To confirm	Needs Review
Equipment preparation is overdue	Prepare	Inventory & Gear	Required group equipment is not prepared before departure.	Primary: OperationsEscalation: Head Guide when fishing delivery is at risk	Primary: To confirmBackup: To confirm	Needs Review
Selected Access is unavailable	Prepare	Accesses & Landowners	The selected Access path or agreement is invalid for the Program date.	Primary: OperationsEscalation: Head Guide for fishing choice; Executive for external commitment	Primary: To confirmBackup: To confirm	Needs Review
Access-owner message is due	Prepare	Accesses & Landowners	A required owner notification has not succeeded by the cutoff.	Primary: OperationsEscalation: Executive	Primary: To confirmBackup: To confirm	Needs Review
Program changed after owner notification	Prepare	Accesses & Landowners	A material Program change has not been redelivered successfully.	Primary: OperationsEscalation: Executive	Primary: To confirmBackup: To confirm	Needs Review
Departure is overdue	Now	Fishing Operations	A ready Program has not started after its departure grace period.	Primary: Daily Guide Coordinator dutyEscalation: Head Guide; Operations for logistics	Primary: Dynamic from lodge/day dutyBackup: To confirm	Needs Review
Active Program GPS is stale	Now	Operations & Readiness	An active Program has no accepted point inside the freshness window.	Primary: Daily Guide Coordinator duty for guide contactEscalation: Head Guide; Support for telemetry failure	Primary: Dynamic from lodge/day dutyBackup: To confirm	Needs Review
Expected tracking never started	Now	Operations & Readiness	Expected tracking did not start after departure.	Primary: Daily Guide Coordinator duty for guide contactEscalation: Head Guide; Support for telemetry failure	Primary: Dynamic from lodge/day dutyBackup: To confirm	Needs Review
Expected return is overdue	Now	Fishing Operations	An in-progress Program has not returned by its expected window.	Primary: Daily Guide Coordinator dutyEscalation: Head Guide; approved safety policy when risk is suspected	Primary: Dynamic from lodge/day dutyBackup: To confirm	Needs Review
Field issue needs follow-up	Now	Fishing Operations	A guide-recorded field issue requires an operational response.	Primary: Daily Guide Coordinator dutyEscalation: Head Guide; Operations for cross-scope recovery	Primary: Dynamic from lodge/day dutyBackup: To confirm	Needs Review
Guide safety alert	Now	Operations & Readiness	A confirmed emergency signal is active.	Primary: Designated El Encuentro safety incident leadEscalation: Head Guide and Executive; relevant Lodge Manager notified	Primary: To confirmBackup: To confirm	Needs Review
Beat cannot be plotted	Now	Field Knowledge	An active or upcoming Program uses a Beat without usable geography.	Primary: Head GuideEscalation: Operations when live visibility is affected	Primary: To confirmBackup: To confirm	Needs Review
Program execution is not closed	Close	Fishing Operations	A returned Program remains in progress.	Primary: Daily Guide Coordinator dutyEscalation: Head Guide	Primary: Dynamic from lodge/day dutyBackup: To confirm	Needs Review
Fishing Report is overdue	Close	Fishing Operations	A required Fishing Report has not been submitted after return.	Primary: Assigned Fishing GuideEscalation: Daily Guide Coordinator duty, then Head Guide	Primary: Dynamic from the ProgramBackup: Dynamic from lodge/day duty	Needs Review
Equipment remains outstanding	Close	Inventory & Gear	Checked-out trip equipment remains outstanding after return.	Primary: Assigned Fishing Guide for the return actionEscalation: Operations for custody recovery; Head Guide for guide follow-up	Primary: Dynamic from the ProgramBackup: To confirm	Needs Review
Client feedback needs attention	Close	Clients & Guest Experience	Eligible feedback requires an operational response.	Primary: OperationsEscalation: Executive for safety, welfare, or unresolved client impact	Primary: To confirmBackup: To confirm	Needs Review
Operational closure is blocked	Close	Operations & Readiness	Trusted source scopes still expose required closure blockers.	Primary: OperationsEscalation: Exact source owner; Executive at the approved cutoff	Primary: To confirmBackup: To confirm	Needs Review
Operational notification failed	Platform	Platform & Support	A required notification reached a terminal delivery failure.	Primary: SupportEscalation: Operations; Executive when a commitment is blocked	Primary: To confirmBackup: To confirm	Needs Review
Field signals are not reaching Operations	Platform	Platform & Support	Mobile or server field signals remain queued or stale.	Primary: SupportEscalation: Operations and Head Guide during active field work	Primary: To confirmBackup: To confirm	Needs Review
Operations data is stale	Platform	Platform & Support	The Operations aggregate exceeds its certified freshness window.	Primary: SupportEscalation: Operations when live decisions are affected	Primary: To confirmBackup: To confirm	Needs Review

Approved access catalog · shadow rollout active

Roles, access, and assistant boundaries

This catalog is implemented in Trailhead's canonical shadow model and visible in Company Settings. Shadow assignments are audit evidence while legacy authorization still controls effective access, so they are not proof that every current account already matches the target. Review actual assignments before canonical cutover and after every role change.

Open the permanent documentation →

Access is the result of five gates

A job title by itself is never enough. Native pages, APIs, reports, and the assistant must all pass the same five checks.

1Identity — the signed-in person and active company are known.
2Product access — Trailhead or SettleWise entry is explicitly enabled.
3Role — a stable job profile supplies a bounded set of permissions.
4Action permission — the exact read, change, or approval is allowed.
5Scope — the company, workspace, lodge, assignment, or self boundary still applies.

One question must produce role-appropriate answers

For the question “How are we doing this season?”, the assistant changes the lens—not only the wording.

Role	Permitted answer	Must leave out
Trailhead Executive	Commercial and operating performance, Analytics, risks, and decisions that need executive attention, with confirmed facts and forecasts kept separate.	SettleWise Accounting, Inventory, Treasury, and Chart of Accounts unless separately assigned.
Trailhead Sales	Confirmed revenue-bearing and FOC bednights, classification completeness, commercial target progress, conversion, pipeline as forecast, and client-readiness blockers.	Analytics, Settings, costs, cash, margin, internal strategy, operations-only detail, Guide schedules/private data, and Chart of Accounts.
Operations	Operating demand, readiness, CIS, Programs, Fishing Guide, Assistant and POA assignments, reports, and blockers needed to run the season.	Analytics, Settings, people/role administration, and Program-conflict resolution.
Head Guide	Fishing-delivery readiness, Guide capacity, Fishing Guide, Assistant and POA assignments, field risks, reports, and Program conflicts escalated for a final decision.	Analytics, Settings, people/role administration, and SettleWise workspaces.
Lodge Manager	Only the current daily and weekly operating context: CIS read-only, today's Guests, weekly meals, relevant notifications, and preference notes.	Company season totals, CIS editing, assignments, Programs, Accesses, Knowledge, Analytics, Settings, finance, and other Guest profile fields.
Fishing Guide, POA Guide, or Assistant	Own assignments, safe trip context, personal readiness, and permitted field references.	Lodge or company season totals, targets, other people's information, finance, and strategy.

Trailhead company-role matrix

A person has at most one Trailhead company role. A field role may be added only when the person genuinely performs both jobs. Guide Coordinator is a daily lodge duty selected from explicit guide ranking, not another company role. Trailhead does not need workspaces today.

Role	Primary lens	May see	May change or decide	Explicit boundary
Trailhead Executive	Business and security authority	All Trailhead business and operational information, including Analytics, Settings, people, roles, and management reporting.	Manage Settings, people and roles, Accesses, and high-impact business decisions.	Field assignments and Program-conflict resolution are reserved for the named operational roles; SettleWise workspaces unless assigned independently.
Trailhead Sales	Commercial work	Commercial workflow, client readiness, Light CIS, commercial reporting, and minimum Guide availability for requested dates.	Maintain the commercial pipeline and create Light CIS records.	Analytics, Settings, finance, Guide schedules/private data, assignments, operations mutation, people/roles, and Chart of Accounts.
Operations	Operations	CIS, Programs, Guests, Fishing Guide, Assistant and POA assignments, weekly meals, Accesses, Knowledge, Gear, reports, and operational blockers.	Run ordinary operations and assign Fishing Guides, Assistants, and POA Guides.	Analytics, Settings, people/roles, Program-conflict resolution, and SettleWise workspaces.
Head Guide	Fishing delivery leadership	All approved Trailhead operational information needed to lead fishing delivery, including roster, readiness, alerts, and Program conflicts.	Assign Fishing Guides, Assistants and POA Guides, make the final decision on escalated Program conflicts, maintain Guide readiness, and resolve operational red flags. A Head Guide may separately hold the daily Guide Coordinator duty.	Analytics, Settings, people/roles, and SettleWise workspaces.
Lodge Manager	Daily guest service	CIS read-only, today's Guests, weekly meals, and relevant notifications.	Edit Guest preference notes only.	CIS editing, assignments, Programs, Accesses, Knowledge, Analytics, Settings, people/roles, finance, and all other Guest profile fields.

Field-role matrix

Fishing Guide, POA Guide, and Assistant access remains limited to the person and their own assignments. The daily Guide Coordinator receives only the conflict capabilities for the assigned lodge and operational day. One current lodge does not justify broad company access.

Role	Primary lens	May see	May change or decide	Explicit boundary
Fishing Guide	Own field work	Own assignments, safe trip context, signals, and self profile/account.	Submit own field updates, Fishing Reports, alerts, and seasonal-kit request.	Other people, other assignments, lodge portfolios, roster, finance, and approvals.
Guide Coordinator · daily duty	Lodge conflict coordination	Shared Program conflicts, affected Programs, and safe alternatives for the assigned lodge and operational day.	Resolve routine Program conflicts in mobile or escalate the complete conflict to Head Guide. The duty starts with the lodge-local day, follows explicit guide ranking, and accrues USD 30 once per guide and date.	This is not a permanent company role and grants no authority over another lodge or day, Guide roster, people, Settings, finance, or Head Guide final escalation unless the person independently holds that role.
POA Guide	Own POA work	Own POA assignments, permitted POA context, weekly meals, and self profile.	Maintain own POA Program activity and request own seasonal kit.	Fishing Reports or any other report submission, Fishing Guide/Assistant work, assignments, company totals, finance, and approvals.
Assistant	Own supporting work	Own assignments, safe field references, weekly meals, and self profile.	Request own seasonal kit only.	Reports, Programs, operational mutation, other people or assignments, company totals, roster, finance, and approvals.

Effective access

How Tomas's access is composed

Tomas performs three independent jobs across two products. Each assignment contributes only its own capabilities and boundary.

PersonTomas

Approved role

Trailhead

Head Guide

What this assignment enables

Assign Fishing Guides, Assistants, and POA Guides
Resolve Program conflicts and operational red flags
Manage Guide readiness and fishing delivery

Boundary

No Analytics, Settings, people/role administration, or SettleWise workspace access.

Independent workspace role

SettleWise · Inventory

Inventory Operator

What this assignment enables

Read products, stock, locations, and availability
Prepare and reconcile seasonal-kit and Gear movements
Perform approved ordinary Inventory operations

Boundary

Inventory only. It grants no Treasury, Accounting, Chart of Accounts, or Trailhead authority.

Viewer or Operator

SettleWise · Treasury

Treasury role to confirm

What this assignment enables

Viewer: read the approved Treasury information
Operator: execute ordinary Treasury work if approved
Use only the actions selected for Tomas's real duties

Boundary

Entry alone grants no write access and never unlocks Accounting or the Chart of Accounts.

Effective access

Three assignments, evaluated together

Tomas can lead Trailhead fishing operations, operate SettleWise Inventory, and use only the approved Treasury actions. Every request still checks the product, assignment, action, and boundary.

Why the assignments stay separate

Inventory and Treasury are not added to Head Guide. A future Head Guide receives only Trailhead capabilities, while Tomas's SettleWise responsibilities can change without redefining the Trailhead role.

Mutation and approval rules

Read access does not imply write access, and ordinary work does not imply approval authority.

Action	Who may do it	Required boundary
Invite members or change standard Trailhead access	Trailhead Executive	Same company only; no self-promotion; every change is audited. Martin and Benja are the intended Executive holders, but authorization is role-based.
Create or edit Guide roster and eligibility records	Head Guide	Roster mutation remains separate from assignment coordination.
Assign or reassign a Fishing Guide on a CIS	Operations or Head Guide	Eligible Fishing Guides only. The CIS and Guide must be in scope, and the server rechecks availability at confirmation.
Assign or reassign an Assistant on a CIS	Operations or Head Guide	Eligible Assistants only. This capability never grants Fishing Guide or POA assignment.
Assign or reassign a POA Guide	Operations or Head Guide	Eligible POA Guides only. This capability never grants Fishing Guide or Assistant assignment.
Resolve a Program conflict	Daily Guide Coordinator; Head Guide after escalation	Guide Coordinator is selected per lodge and local day from the top-ranked active guide working there. The server rechecks current duty ownership, conflict revision, alternatives, and impact before confirmation; Head Guide is the final authority only after escalation.
Edit a Guest preference note	Lodge Manager, Operations, Head Guide, or Trailhead Executive	Preference-note field only. No identity, profile, commercial, or financial field may change.
Create or update ordinary operating records	Operations, Head Guide, or Trailhead Executive; Fishing Guide or POA Guide only for explicitly permitted own work	The exact permission and resource scope must be checked for every change.
Maintain commercial pipeline or create Light CIS	Trailhead Sales or Trailhead Executive	Commercial scope only; handing a confirmed trip to Operations does not grant operational mutation.
Review or confirm weekly meals	Operations, Head Guide, or Trailhead Executive	Lodge Manager, POA Guide, and Assistant may read the safe weekly view but cannot review or confirm it.
Read, post, approve, or configure SettleWise Accounting	The matching SettleWise Accounting workspace role	A Trailhead role never supplies this authority. Operator and Approver remain separate unless an audited exception is approved.
Prepare or confirm an action through the assistant	Only a person already authorized for the same native action	The assistant rechecks role, scope, target, and confirmation at execution time. A prompt never grants authority.

Assistant enforcement rules

The assistant has no special AI role. It projects the person's current access and must become narrower whenever the person's scope is narrower.

1. Resolve the signed-in person's current product, role, action permission, and scope before reading data or mounting a tool.
2. Use the role's permitted lens. Do not create one generic management answer and merely hide a few fields.
3. Never reveal that an inaccessible record, lodge, person, metric, or account exists.
4. Keep confirmed actuals, active holds, pipeline forecasts, targets, and financial bases explicitly separate.
5. A read may summarize or deep-link. A mutation requires the native action permission, an in-scope target, explicit confirmation, and an audit event.
6. After any role or scope change, discard prior pending confirmations and calculate access again.

Client review checklist

Name one accountable owner for each role and every high-impact approval.
List each person's Trailhead company role, field role, and separate SettleWise workspaces.
Test at least one permitted read, one refused read, one permitted mutation, and one refused mutation per role.
Repeat the same checks through the assistant; a prompt must never widen access.
Revoke old invitations, legacy flags, and stale assignments after the new role is active.

Core operating loop

Supporting product areas

CIS

How this percentage is calculated

What works today

What remains

Alpha 1 candidate focus

Implemented baseline

Open before go/no-go

Owns

Boundary

Alpha 1

After Alpha 1

Later

Owns

Boundary

Alpha 1

After Alpha 1

Later

Owns

Boundary

Alpha 1

After Alpha 1

Later

Owns

Boundary

Alpha 1

After Alpha 1

Later

Owns

Boundary

Alpha 1

After Alpha 1

Later

Owns

Boundary

Alpha 1

After Alpha 1

Later

When scopes meet on mobile

Shared or unassigned ownership

Trips & CIS

Guides & Assignments

Clients & Guest Experience

Travel & Handoffs

Fishing Operations

Accesses & Landowners

Guide Accounts & Payments

Operations & Readiness

Inventory & Gear

From booking to a trip-ready CIS

Management reports

Beds & access usage

Daily operating health

Trip delivery and outcomes

Financial exposure

Open exceptions

Client demographics and retention

Equipment stock coverage

Nationality and market mix

New and returning clients by age

Clients by state and city

Client data quality

Alerts & responsibilities

Roles, access, and assistant boundaries

Access is the result of five gates

One question must produce role-appropriate answers

Trailhead company-role matrix

Field-role matrix

Mutation and approval rules

Assistant enforcement rules

Client review checklist