Path A
Start with the free path
If you are still deciding whether this platform is the right fit, start with the public experience path before deciding whether to register, log in, or discuss a real scenario.
Start Here
Start Here
Guide FirstOn a first visit, the biggest time sink is usually not missing features. It is not knowing which path to start with.
This page separates the entry points, user roles, and reading path before you go deeper.
This guide helps first-time ExecGov visitors decide whether they should start with the free path, expand personal local script slots, move into the standard team edition, or go straight into an enterprise delivery conversation.
Try firstLocal script slotsStandard team editionCLI bridgeEnterprise delivery
EXECGOV // START HEREGUIDE 01
const firstVisit = ['free_entry', 'login', 'core_docs']const localPath = ['local_scripts', 'cli_bridge', 'manifest', 'run']const deliveryPath = ['tenant_delivery', 'delivery_docs', 'hot_update']
PICK THE PATH THAT MATCHES YOUR STAGE
Path B
Personal continuation / local script slots
If you are already connecting scripts in your personal space but have not moved into multi-user collaboration yet, review local script-slot expansion and CLI boundaries before switching to enterprise-delivery language.
Path C
You need the standard team edition
If your focus is multi-user collaboration, formal tenants, and a stable usage cycle, start with billing, membership, customer flow, and the shared-SaaS boundary.
Path D
You need enterprise delivery
If you are here with a client project, intranet constraints, private deployment, or formal acceptance requirements, focus on customer flow, deployment, and delivery boundaries rather than free-entry details.
Public Entry
Current public entry points that are officially available
| Entry type | How to understand it today | Best for | What to read next |
|---|---|---|---|
| Public experience flow | You can now enter from /experience, /login, and /register directly for the experience and signup flow | People touching the platform for the first time | Getting Started |
| Product docs | Explains what the platform is, how delivery works, how deployment works, and how it evolves | Product, presales, and technical leads | Product Overview |
| CLI docs | Explains the current boundary of local login, capability registration, execution, and the Agent skeleton | Developers and local-bridge scenarios | CLI Guide |
| Customer delivery docs | Explains how customers use the platform, how delivery works, and how script hot updates are handled | Delivery owners and project owners | Customer Flow / Delivery |
| Contact entry | Used for four-way routing: the free path, local script slots, the standard team edition, and enterprise delivery | People who want to move forward | Lead routing |
Role Based
Where different roles should start
Individual developers
Start with Getting Started, then the CLI Guide, then decide whether you need a deeper team or enterprise path.
Small-team owners
Start with Product Overview, Billing & Membership, and Customer Flow / Delivery, then decide whether the standard team edition is enough or whether you need to move up into enterprise delivery.
Presales / solution roles
Start with the materials, then return to Product Overview, Deployment, and Customer Flow to establish a consistent narrative.
Enterprise customers
Start with Customer Flow / Delivery and Deployment, then confirm tenant isolation, hot-update boundaries, and the follow-up collaboration model.
Reading Order
Enter by goal
Step 01Getting Started
First confirm the public entry points, experience path, and current capability boundary.
Step 02Product OverviewThen understand what the platform is, which scenarios it fits, and which capabilities are already available.
Step 03Customer Flow / DeliverySee how customers use it, how delivery works, and how script hot updates are currently closed-looped.
Step 04Onboarding ChecklistWhen preparing a real project, use this to align the script directory, README, example files, and boundary information in one pass.
Step 05Files & ResultsIf the task depends on input files, output files, or report artifacts, this page is more practical than a generic product description.
Step 06CLI GuideIf you already have a local script directory, this page is more useful than a broad introduction.
Step 07FAQUse it to settle questions such as whether this is just a chat product, whether tenants can leak into one another, or whether it can be used for real delivery now.
Step 08MaterialsIf you need presentation, scenario, or solution-communication assets, continue from there.
Project Ready
Common materials for real projects
DeliverablesDeliverables
Clarify what entry points, instructions, and result artifacts the customer will finally receive before the delivery phase gets messy.
ChecklistOnboarding ChecklistUseful for presales, implementation, and the customer to align script directories, README files, examples, dependencies, and risk boundaries together.
FilesFiles & ResultsIf the project is file-driven, report-driven, or artifact-driven, this page should be reviewed before rollout rather than patched in afterward.
Next Step
If you want to move forward, choose the next page by goal
The free path, local script slots, the standard team edition, and enterprise delivery all exist, but they should not be mixed together.