Chapter 14: Glossary
Use the glossary when a label, state, or route explanation feels meaningful but not yet actionable. The definitions here are written to support decisions. They explain what the term means in the product and why it matters to the next step.
Entitlement
Entitlement is the product’s way of deciding whether a capability is available in the current account state. It explains why a signed-in user can still encounter a lock, a trial limitation, or a route-specific invitation instead of live guidance. Sign-in is identity. Entitlement is access. Deliverable state is readiness. Security confirmation is a separate trust layer.
Use the glossary when a route, label, or state seems clear enough to be meaningful but not clear enough to be actionable. The definitions here are intentionally practical. They are written to help you decide what to do next, not just to memorize vocabulary.
Aegis
The in-product guidance assistant that interprets the route you are on, explains next steps, and either provides live structured guidance for entitled users or returns a polished membership invitation for explorers who have not activated a trial or paid plan.
Aegis action surface
The part of the Aegis widget that focuses on concrete next steps rather than free-form conversation. Use it when you want route-aware actions without composing a long prompt.
Aegis chat surface
The conversational pane inside the Aegis widget. It is best used for scoping, interpretation, and route-specific questions grounded in the page you are currently viewing.
Aegis fallback
The controlled response path used when live guidance is not available for the current account state. In production this path is intentionally graceful and commercial: it explains how to activate access instead of exposing raw internal denial language.
Aegis live guidance
The entitled path in which Aegis can provide live structured assistance. In the current product, active trial users and active paid users are the intended commercial states for live guidance.
Anchor
A stable section link within the manual. Context help uses anchors to open the exact explanatory section that matches the route or state a user is currently seeing.
Analysis execution
The act of running a selected lens or lens set against a deployment description to create or update structured output. Browsing the catalog is public; execution remains server-gated by plan and entitlement.
App route
A page path inside the product application, such as /dashboard, /billing, or /deliverables. The manual is written route-first so users can map what they see on screen to the right explanation quickly.
Assumptions and limits
The part of a deliverable that makes the scope explicit. Strong 7DEA usage depends on reviewing assumptions early, because the quality of the scope statement directly affects the quality of the resulting draft.
Audit history
The visible record of account-relevant actions such as security changes, profile updates, and data-rights activity. It helps users confirm what has happened on the account without inferring from memory.
Audit Pack ZIP
A premium export format that bundles machine-usable material around a deliverable. Trial limitations can lock this export, so users should treat the visible entitlement state as the source of truth for availability.
Audit-ready
A product promise about structure and traceability, not a blanket claim that a deliverable alone resolves every legal or operational obligation. Audit-ready in 7DEA means the output is organized for review, evidence gathering, and next-step planning.
Authenticated startup walkthrough
The recommended first pass through the product after sign-in. It starts on the dashboard, confirms plan and account state, and then routes the user toward the right next action.
Baseline
The starting perspective from which overlays are compared. In 7DEA, the Universal lens is the normal baseline because it gives users a cross-jurisdiction governance starting point before more specific overlays are added.
Billing portal
The hosted billing-management surface used for plan and payment-management tasks. It is separated from the app’s own account surfaces so sensitive payment administration can happen through the billing provider’s supported flow.
Build identifier
The short release identifier shown in the trust bar. Users rarely need it for ordinary work, but it is helpful when reporting a reproducible issue because it ties the visible experience to a specific deployed build.
Cancel trial
The action that stops automatic conversion after the trial period. Canceling a trial is different from deleting an account; it changes billing outcome without erasing account history or current access immediately.
Cancellation scheduled
A billing state that tells you the account still has access until the current paid or trial period ends, but is not set to continue automatically after that horizon.
Catalog version
The visible version label on the lens catalog. It is a compact indicator that the list you are reviewing is a managed product surface, not a loose collection of unversioned policy pages.
Certified output
A user-facing way of describing a Final deliverable that has moved beyond draft and into download/share readiness. In practice, the route still displays the precise state terms such as Draft or Final.
Checkout
The paid-activation flow that starts from the Plans page and continues in Stripe-hosted surfaces. 7DEA makes the plan decision visible before redirecting so the user understands what they are buying and why.
Commercial coherence
The alignment between the pricing surface, entitlement behavior, Aegis behavior, and user expectations. A commercially coherent system does not promise one state while the runtime behaves as though a different state is active.
Context help
The route-aware set of manual links shown inside the app. It is designed to shorten time to understanding by opening the exact section most likely to answer the question raised by the page you are on.
Controlled distribution
The practice of sharing deliverable output through managed channels, especially revocable share links and explicit export actions. 7DEA treats shareability as a governed capability, not a side effect.
Current page context
The route, selections, and recent history that Aegis uses to make its guidance relevant. Good Aegis prompts usually reference the page and the decision you are trying to make there.
Customer-facing manual
The public documentation published at https://7dea.ai/docs. It is intentionally separated from internal runbooks so users get accurate product truth without private operational detail.
Data export
The account-rights action that prepares a user-visible export of their account data. It is intentionally protected by re-auth flows because it is both privacy-sensitive and operationally meaningful.
Data rights
The user’s ability to request account-level actions such as export or deletion through the product. 7DEA explains these in plain language while still requiring stronger confirmation for sensitive tasks.
Decision support
The class of assistance 7DEA provides. The platform structures obligations, controls, and next actions, but it does not replace professional legal, regulatory, or organizational judgment.
Deterministic draft
The immediate deliverable produced from the submitted scope. Deterministic draft means the user gets a structured output quickly, even when later steps such as Final PDF publication depend on processing windows.
Divergence
A comparative lens term used when an overlay lens introduces obligations or perspectives that meaningfully differ from the baseline. Divergence does not automatically mean conflict; it means additional interpretation work is required.
Download PDF
The export action used once a deliverable reaches Final. If the control is locked or disabled, the correct interpretation is to confirm entitlement and state rather than trying to force the action.
Draft
The initial visible deliverable state. A Draft is meant for scope review, early discussion, and correction before the later Final publication step makes the PDF and share actions available.
Entitled user
A user whose current account state permits the requested capability. In the Aegis context, entitlement governs whether live guidance is available. In the export context, it governs which formats and sharing actions are unlocked.
Entitlement
The combination of account state and plan state that determines whether a capability is available. Entitlement is always more reliable than assumption: if the UI says a feature is locked, treat that as runtime truth until the billing or account state changes.
Explorer
A non-entitled visitor or signed-in account that has not activated a trial or paid subscription. Explorers can still learn, browse the catalog, and use public docs, but they should not consume live paid guidance capacity.
Evidence trail
The set of facts, assumptions, state labels, and artifacts that make a deliverable understandable and reviewable. In strong practice, users add their own organizational evidence around the deliverable rather than treating the platform output as a closed world.
FAQ
The frequently asked questions section of the manual. In 7DEA, FAQ is meant to speed interpretation, not replace route-specific reading of the live UI.
Feature lock
A visible indicator that a capability is unavailable in the current state. The phrase next to the lock is usually more important than the lock itself, because it tells you whether the reason is plan, processing state, or some other readiness requirement.
Final
The deliverable state that unlocks the finished PDF and, when entitled, sharing actions. Final is the clearest signal that the draft has completed its current processing cycle.
Final PDF
The finished PDF output associated with a Final deliverable. Users should treat its availability as a result of both state and entitlement: a deliverable must be Final, and the account must have access to that export capability.
First-time checklist
The dashboard list that updates as your account advances through plan selection, deliverable creation, PDF availability, and optional sharing. It is one of the fastest ways to see what 7DEA thinks your next safe step should be.
First-session quickstart
The beginner path that takes a new user from sign-in to a first meaningful result without assuming expert knowledge of every page. The manual preserves this as a stable reference because it matches live context-help behavior.
Guided onboarding
The structured Aegis-led flow that turns early questions into a concrete first deliverable path. It exists to reduce the blank-page problem and make the first submission more deliberate.
Human review
The expectation that people still interpret the output, confirm scope, and decide what to do next. 7DEA is strongest when used as a disciplined collaborator, not as an excuse to skip review.
Intent phrase
A natural-language phrase associated with a help-map entry. Intent phrases let context help and support workflows map user questions to the correct manual section more quickly.
Jurisdiction overlay
A lens that adds region-specific obligations or interpretation on top of the Universal baseline. Overlays are most useful when your deployment scope clearly touches the geography or legal framework represented by the lens.
Lens
A structured perspective used to interpret a deployment or deliverable. Some lenses represent broad governance standards, while others capture jurisdiction-specific or status-tracked regimes.
Lens catalog
The browsable registry of currently available lenses. It helps users decide what to include before they run analysis or create deliverables, and it remains accessible even before a user becomes a subscriber.
Lens family
A broad category such as baseline, standards-oriented, jurisdictional overlay, or status-tracked. Families help users understand what a lens is trying to contribute before they decide whether to include it.
Lens selection
The process of choosing which lenses should shape a deliverable. In 7DEA, better selection usually starts with Universal, then adds only the overlays needed for the real operating context.
Live guidance
The Aegis mode that uses live back-end assistance for trial and paid users. It is distinct from static page copy and from the controlled fallback response shown to explorers.
llm_fallback
The user-visible path label that indicates Aegis is serving the controlled non-live response path. In practice this means the user can still receive direction, but not live paid guidance.
llm_live
The user-visible path label that indicates live Aegis assistance is active. This is the production proof point that a properly entitled account is reaching the live guidance path.
Membership invitation
The fallback response shown to explorers who try to use live Aegis without entitlement. It is designed to be respectful, clear, and commercially useful rather than punitive.
Multi-lens comparison
The practice of evaluating how the Universal baseline and one or more overlays align or differ. It is often the right move when your deployment spans multiple jurisdictions or needs more than one governance frame.
Non-entitled state
Any state in which the account does not currently have the right to use the requested capability. For Aegis, that includes explorer paths; for exports, it can include trial or lower-tier limits even after sign-in.
Onboarding path to draft creation
The part of guided onboarding that moves a user from general questions into a concrete deliverable-creation step. It is one of the highest-value transitions in the platform because it turns intent into output.
OTP
One-time password. 7DEA uses email OTP as the primary sign-in pattern, which keeps access simple while still requiring explicit proof of control over the mailbox used for the account.
Page context
The combination of current route, current selections, and recent user action that shapes contextual guidance. Aegis and the context-help panel both use page context to stay useful.
Paid membership
An active plan that unlocks the paid capability set for the account. Paid members are the intended durable commercial state for recurring live Aegis usage and for broader export/share capability.
Past due
A billing state that signals the account needs payment attention. Users should treat past-due states as real access constraints and resolve them through billing workflows rather than assuming the previous entitlement still applies.
Pilot
The entry paid tier intended for individuals or smaller teams validating a recurring governance workflow. The billing page is the source of truth for its live entitlements and limits.
Plan context
The current subscription state the product is showing you, including whether you are in trial, active, canceled, or otherwise gated. Plan context is the explanation layer behind many locked or available controls.
Plan overview
The billing page explanation of the currently active or available tiers. It is the correct place to confirm what will unlock if the user starts a trial or subscribes.
Processing window
The governed time window during which certain background publication actions complete. Users mostly encounter this through Draft-to-Final timing and through language that explains why finalization is waiting.
Profile
The personal account information visible on the Account page. Profile management is intentionally separated from billing and from data-rights operations so each category remains clear.
Queued
The intermediate state in which a deliverable or publication step is waiting for processing. Queued is not necessarily a failure; it often means the system is waiting for the next allowed window to complete Final publication.
Renewal
The next date on which an active paid plan is expected to continue unless canceled. Renewal language helps users distinguish an active subscription from a trial or a scheduled cancellation state.
Re-auth
The short additional verification step required for sensitive account operations such as email changes or data-rights actions. Re-auth exists because some actions are more sensitive than ordinary page browsing.
Revocable share link
A share URL the account owner can later disable. It is designed for controlled distribution of finalized outputs rather than permanent public publication.
RPIM
A product term used on the public docs and signal-related pages to describe external signal interpretation within the platform. The public manual explains where it appears and how to interpret it without exposing private operations.
Scope statement
The description of the AI deployment, use case, jurisdictions, users, and risk context that the user submits. Strong scope statements are the single biggest contributor to strong draft quality.
Security session
One of the active login sessions visible on the account security surface. Reviewing sessions helps users confirm whether access is limited to the devices they expect.
Session required
A page state that means the surface is account-scoped and cannot load fully until the user signs in. When you see this state, the fix is authentication, not repeated refreshes.
Share or revoke share
The control used to publish or disable a managed share link. Because it changes distribution posture, it is treated as a deliberate action rather than an automatic side effect of creating a deliverable.
Signal sync
A catalog indicator showing whether a lens has an associated external update signal, a status-tracked relationship, or no active signal feed in the current product. Signal sync describes freshness posture, not guaranteed legal completeness.
Start Here
The fast-path route for users who want the shortest route from orientation to first deliverable. It functions as a practical launch pad rather than a full manual replacement.
Status-tracked
A lens or signal state that indicates the product is monitoring the status of a framework or regime, even if it is not presented as fully in-force guidance. Users should treat status-tracked items as context requiring interpretation.
Structured assistance
Aegis help that is grounded in page context, user state, and workflow progression rather than open-ended brainstorming alone. It helps 7DEA stay action-oriented.
Subscription active
The billing state that confirms the account currently has an active paid plan. In the dashboard this often appears alongside plan name and renewal information.
System mode
The trust-bar label that tells you whether the system is operating in its normal governed mode. Users do not need the internal mechanics; they do need to know that the label explains why some publication steps may wait.
Team seat
A plan-level capacity concept described on the billing surface. It helps buyers understand how the product is positioned for solo operators, growing teams, or enterprise rollouts.
Token status
The visible indicator on some account actions that a stronger confirmation step is still missing. It is a clue that the user needs to complete re-auth before sensitive actions can proceed.
Trial
The limited commercial activation state used to let users experience the product before full subscription. In the current product, trials enable live Aegis but still lock selected export and sharing actions.
Trial day counter
The visible indication of how many days remain in the current trial. It helps users understand both access horizon and the urgency of a decision to continue or cancel.
Trial limitations
The explicit list of features that remain locked during the trial. Because this language is shown directly on the billing page, it should be treated as canonical product truth.
Trust bar
The visible summary strip that shows system mode, billing mode, uptime, and build information. It is designed to make state legible without requiring users to infer it from hidden internals.
Universal
The default baseline lens used almost everywhere as the safest first pass. Universal gives users a cross-jurisdiction governance reference before more specific overlays are introduced.
Uptime
The duration indicator shown in the trust bar. It gives users a quick feel for service continuity without requiring them to inspect a separate operational dashboard.
Version changes
The customer-readable explanation of what is live now and how recent product changes affect the user journey. It is distinct from the internal engineering history.
What this page does
The short descriptive paragraph near the top of many routes. It is one of the most valuable pieces of onboarding copy in the product because it tells the user the purpose of the page in plain language.
Windowed
A user-visible state term indicating that some governed actions publish within allowed windows rather than instantly at any moment. Users do not need to know the private scheduling implementation to use the product effectively.
Workflow gate
Any state-based condition that prevents an action from proceeding. In practice the gate may come from plan state, account state, processing state, or a required confirmation step such as re-auth.
Baseline-first strategy
The practical habit of starting with the Universal lens and only then adding overlays that reflect genuine jurisdictional or standards obligations. This strategy reduces noise and keeps the first deliverable interpretable.
Build identifier
The short release label surfaced to users in the trust bar. It is especially helpful when comparing behavior across sessions or reporting a reproducible issue to support.
Checklist completion
The dashboard’s way of showing whether the account has completed foundational milestones such as choosing a plan or generating a first deliverable. It is a workflow cue, not a scorecard.
Commercial invitation
The respectful fallback language that explains how a user can activate trial or paid access. In the Aegis context, it replaces raw technical denial with a user-understandable next step.
Controlled capability
A product capability that is intentionally governed by entitlement, state, or stronger confirmation rather than being universally available after sign-in.
Docs route
The public manual experience at /docs. It functions as a live support layer with stable anchors, not merely as a marketing appendix.
Evaluation workflow
The path taken by an explorer or early-stage reader who is still assessing fit. It often emphasizes docs, lens catalog, and plan comparison before any trial or paid activation.
Fast path
The concise route sequence surfaced on Start Here for users who want the shortest journey to a first meaningful result.
First deliverable posture
The idea that the first deliverable should be concrete, reviewable, and proportionate rather than maximal or over-engineered.
Freshness posture
The public-facing way a catalog item signals how much change-awareness or update-awareness the user should bring to its interpretation.
Governance window
A public-safe way to describe the controlled timing model for certain publication-sensitive actions. It explains why Draft and Final can arrive on different schedules.
Help-map anchor
A stable route-to-manual linkage point used by context help so a user can jump from a page or state directly to the relevant explanation.
Interpretation layer
Any part of the product that helps explain what another part of the product means. The manual and Aegis both act as interpretation layers for the live UI.
Operational fit
The degree to which the product’s live workflow, lens posture, and deliverable outputs match the real needs of a team or organization.
Page owner
The category of product truth a route is responsible for. Billing owns commercial truth, Deliverables owns output truth, and Account owns account-trust truth.
Payment-method verification
The trial-start step that confirms a valid reusable payment method before trial begins. It helps create a cleaner path from trial to continuation.
Plan fit
The practical match between a plan’s live capability set and the real work a user or team needs to perform.
Procurement posture
The degree to which a team needs commercial clarity, support expectations, or enterprise-oriented planning before adoption.
Public-safe documentation
Documentation written to improve user understanding without exposing internal-only security, infrastructure, or administrative details.
Review cadence
How frequently a team expects to revisit a deliverable, lens set, or signal-sensitive area. Dynamic or status-tracked areas usually deserve a tighter cadence.
Route sequence
The intentional order in which a user moves from one page to another to complete a workflow without losing state clarity.
Session refresh
The act of re-establishing a current signed-in posture after expiry, sign-out, or extended absence. It is separate from any commercial state change.
Share readiness
The combined condition in which a deliverable is Final and the account’s commercial state allows controlled sharing.
State mismatch
A contradiction between two visible truths in the product, such as a billing page that claims active access while another route behaves as if no access exists.
Support packet
The minimal evidence needed for effective troubleshooting: route, timestamp, visible wording, commercial posture, and reproduction steps.
Team workflow
The repeatable pattern a group uses to move from scope statement to deliverable review to distribution and follow-up action.
Trial invitation path
The commercial explanation shown to users who can benefit from live guidance or broader capability only after activating trial or a paid plan.
Usage posture
The overall way a person or team is engaging the product at a given moment: evaluation, trial, paid production, review, or support.