Front Matter
How to use the public manual and how to read route truth, commercial truth, artifact truth, and trust-bar truth.
7DEA User Manual
This manual is the canonical public operating reference for the live 7DEA platform. It is written for people doing real work: evaluating the product, activating access, creating deliverables, reviewing outputs, and interpreting visible system state without guesswork.
26chapters
733linked sections
Route-awarehelp system
Best way to start: read Getting Started, then start a free trial or sign in in the app and ask Aegis: “Help me get started.” Live Aegis guidance is available to trial and paid users.
Multi-Layered Table of Contents
Start with the part that matches your current task, then use the nested chapter links to jump directly into the route, state, or workflow you need.
Manual Part
Part I - Orientation
Getting Started
The best first-session path from sign-in or exploration to a meaningful first draft.
Manual Part
Part II - Core Workflow
Aegis and Guided Onboarding
How Aegis works, when live guidance is available, and how to ask better route-aware questions.
- What Aegis Is Good At
- Guided Onboarding Flow
- Guided Onboarding Path to Draft Creation
- Step-by-Step Walkthrough
- Explorer, Trial, and Paid Aegis Behavior
- Aegis Membership and Live Guidance
- How to Read Aegis Responses Well
- How Aegis Uses Route Context
- What Live Guidance Does and Does Not Change
- Prompt Patterns by Route
- High-Value Prompts for Real Work
- When to Stop Prompting and Start Acting
- When Aegis Defers to Other Surfaces
- Recovering from Interrupted Onboarding
- When Aegis and the Product Seem to Disagree
- Appropriate Use and Responsible Expectations
Lenses and Scope Design
How to use Universal as a baseline, when overlays are justified, and why better scope usually beats accidental complexity.
- Lens Catalog Baseline and Overlay Model
- Lens Catalog Overview
- Universal Lens Snapshot
- Choosing Overlay Lenses Intelligently
- Comparative Mapping and Baseline Interpretation
- Lens Families in Practice
- How Plan State Affects Lens Selection
- Signal Sync, Freshness, and Why Some Lenses Look Different
- Practical Lens Selection Scenarios
- Common Lens Mistakes and Better Alternatives
- When to Move from Catalog to Deliverable Creation
Deliverables and Review
Creating drafts, reading Draft and Final correctly, and improving the artifact through disciplined review.
- Deliverable Lifecycle
- Create a Deliverable Draft
- Reviewing the First Draft Well
- Anatomy of a Strong Deliverable
- Revision Cycles and Version Discipline
- Deliverable Status and Processing Windows
- Export and Share Actions
- Review Meetings and Stakeholder Handoffs
- AI-to-AI Consumption Pattern
- Working with Locked Actions Without Losing Momentum
- Distribution Discipline
- Common Deliverable Questions
- What Good Completion Looks Like
Evidence, Exports, and Audit Readiness
How to think about assumptions, review packets, controlled exports, and downstream use without overstating certainty.
- What Auditability Means in 7DEA
- Reading Assumptions and Limits Early
- Evidence, Human Review, and Organizational Memory
- Building an Evidence Packet Around the Deliverable
- Review Readiness Checklist
- Why Visible State Is Part of Evidence
- Draft Review Versus Final Review
- Briefing Reviewers Well
- What 7DEA Does Not Claim
- Practical Signals of a Healthy Workflow
- Using Deliverables With Executives, Clients, and Partners
- How to Escalate Without Losing Context
- Extended outputs and disciplined downstream use
- Evidence packets and review packets
- What to Preserve After a Review Cycle
Plans, Trials, and Entitlements
How billing explains live product behavior, what trial unlocks, and how to read gates accurately.
- Plan Tiers and Billing Surface
- Plan Overview
- Starting a Trial Safely
- How to Evaluate the Trial Well
- What Each Plan Unlocks
- Reading Plan Value Without Guesswork
- Understanding Gated Controls
- Explorer, Trial, and Paid Commercial Behavior
- Renewals, Cancellation, and Scheduled Change
- Upgrades, Downgrades, and Commercial Transitions
- Choosing the Right Commercial Path
- When Billing Explains Product Behavior Elsewhere
- Verifying payment method for trial
- Checkout success and activation
- When Commercial State Should Trigger a Support Question
Manual Part
Part III - Working With Confidence
Account Security and Data Rights
Profile, sessions, re-auth, billing portal access, audit history, and user-facing rights actions.
- Security Controls You Can Use
- Session Management
- Email OTP Sign-In and Identity Continuity
- Data Rights and Re-Auth Token Workflow
- Data Rights Requests
- Preparing for Sensitive Account Changes
- Profile, Identity, and Change Management
- Billing Portal Access from Account
- Audit History as a Trust Tool
- Team Ownership and Account Stewardship
- Healthy Account Hygiene Practices
- When to Ask for Support
Context Help and System States
How to read trust bars, path labels, queues, locks, and route ownership without overreacting.
- What the trust bar is telling you
- Context help panels
- Aegis path states
- Billing and entitlement states
- Deliverable states
- Queued, locked, and finalizing
- Reading locked controls correctly
- Page ownership matters
- Reconciling state mismatches calmly
- Build identifiers, reproducibility, and calm reporting
- Practical state-reading checklist
Route Reference and Page Playbooks
A practical reading order for the major public and in-app routes, with route-specific signals and next moves.
Role-Based Workflows
How explorers, trial users, paid operators, reviewers, team leads, and support-facing readers should use the same product differently.
- Explorer and evaluator workflow
- Trial-user workflow
- Paid-operator workflow
- Reviewer and approver workflow
- Team lead and governance-owner workflow
- Support and operations workflow
- Executive sponsor and buyer workflow
- Consultant, advisor, and implementation-partner workflow
- Teaching the product to a team
- Designing a Weekly Working Rhythm
Troubleshooting and Support
A state-first troubleshooting method, support packet discipline, and a clear escalation threshold.
- Troubleshooting Workflow
- Diagnosing Sign-In and Trial Activation Questions
- Diagnosing Aegis Questions
- Diagnosing Deliverable Questions
- Diagnosing Billing Questions
- Diagnosing Account and Security Questions
- Diagnosing Docs and Context-Help Questions
- Support Reporting Template
- Support packet checklist
- What not to do while troubleshooting
- When to escalate
- What good evidence looks like
- When a problem is real but not urgent
Manual Part
Part IV - Judgment Guides
Commercial State Guides
Concrete scenarios for reading the difference between sign-in, trial, paid state, cancellation language, and payment attention.
- State Guide 1 — Signed In but Not Yet Commercially Active
- State Guide 2 — Active Trial with Locked Exports
- State Guide 3 — Active Paid Plan with No Deliverables Yet
- State Guide 4 — Cancellation Scheduled but Access Still Active
- State Guide 5 — Past-Due or Payment Attention Required
- State Guide 6 — Explorer Reading the Product Like a Paid User
- State Guide 7 — Trial-to-Paid Conversion Decision
- State Guide 8 — Paid Renewal with New Team Expectations
Lens Choice Guides
Scenario-based guidance for deciding when to stay with Universal, add overlays, compare lenses, or simplify the stack.
- Lens Casebook 1 — Universal Only for an Internal Productivity Assistant
- Lens Casebook 2 — Multi-Jurisdiction Deployment with Real Overlay Need
- Lens Casebook 3 — Standards-Oriented Team Seeking Shared Vocabulary
- Lens Casebook 4 — Status-Tracked Lens for Emerging Regulatory Attention
- Lens Casebook 5 — Too Many Overlays from Stakeholder Anxiety
- Lens Casebook 6 — Starting Simple to Prove Workflow Fit
- Lens Casebook 7 — Signal-Sensitive Catalog Reading
- Lens Casebook 8 — Explaining Lens Choice to a Non-Specialist Reviewer
Deliverable Review Guides
Scenario-based guidance for knowing when to revise, when to wait, when to review, and when to distribute.
- Review Pattern 1 — Draft Review Before Internal Meeting
- Review Pattern 2 — Final Review for Controlled Sharing
- Review Pattern 3 — Revising Scope After a Weak First Draft
- Review Pattern 4 — Translating Deliverable Output for Executives
- Review Pattern 5 — Reconciling Stakeholder Disagreement
- Review Pattern 6 — Using a Final PDF as a Governance Artifact
- Review Pattern 7 — Explaining a Locked Share Control to Stakeholders
- Review Pattern 8 — Turning One Deliverable into a Repeatable Workflow
Team Rollout Patterns
How teams adopt the product responsibly without confusing education, execution, and organizational readiness.
- Team Pattern 1 — Single Operator, Single Reviewer
- Team Pattern 2 — Cross-Functional Review Meeting
- Team Pattern 3 — Procurement-Oriented Evaluation
- Team Pattern 4 — Rolling the Product Out to a New Internal Group
- Team Pattern 5 — Shared Artifact, Different Risk Tolerances
- Team Pattern 6 — Repeating the Workflow Quarterly or on Change Events
- Team Pattern 7 — Explaining the Product to an External Advisor
- Team Pattern 8 — Training a Supportable Culture, Not Just a Tool Habit
Support and Escalation Guides
When to keep reading, when to escalate, and how to distinguish contradiction from ordinary gating or waiting.
- Support Case 1 — The User Reports That Aegis Is Broken
- Support Case 2 — The User Says Download Is Missing
- Support Case 3 — The User Cannot Tell Whether Trial Started
- Support Case 4 — The User Reports a Confusing Session Required Message
- Support Case 5 — The User Says the Product Feels Contradictory After Time Away
- Support Case 6 — The User Wants a One-Paragraph Explanation for Leadership
- Support Case 7 — The User Thinks the Manual and UI Disagree
- Support Case 8 — The User Is Unsure Whether to Escalate or Wait
Adoption and Enablement
How to teach the product, spread vocabulary, and make the manual part of normal working practice.
- Adoption Pattern 1 — Teaching the Product Through the Route Model
- Adoption Pattern 2 — Building Shared Vocabulary Early
- Adoption Pattern 3 — Turning the Manual into a Standing Reference
- Adoption Pattern 4 — Moving from One Champion to a Team Habit
- Adoption Pattern 5 — Explaining the Workflow to Leadership Without Overpromising
- Adoption Pattern 6 — Using Trial as a Structured Evaluation Program
- Adoption Pattern 7 — Aligning Review Culture to the Product’s State Model
- Adoption Pattern 8 — Preparing for a Broader Operating Cadence
Change Awareness and Catalog Freshness
How to read product evolution, catalog freshness cues, and small live changes without confusing them for broken workflow logic.
- What changes slowly and what changes faster
- Signal sync and catalog freshness
- Billing and entitlement changes over time
- Why change awareness matters to users
- How the public manual stays current
- What to do when the docs and product seem out of sync
- Keeping team memory current without overreacting
- The practical baseline
Manual Part
Part V - Reference
Frequently Asked Questions
Short answers to the most common questions about billing, Aegis, deliverables, export locks, and route meaning.
- I can browse the lens catalog without signing in. Why can’t I generate a deliverable from the same surface?
- Why does Aegis sometimes answer with a membership invitation instead of route-specific live guidance?
- What is the safest first deliverable strategy for a new user?
- Why is my deliverable still Draft even though the creation step succeeded?
- Can trial users use Aegis live guidance?
- Why do some buttons say locked even after I signed in?
- What should I send support when something feels inconsistent?
- How should I think about the difference between the dashboard and Start Here?
- What does ‘Windowed’ mean in the trust bar or Aegis widget?
- Can I share a deliverable before it is Final?
- Is the manual a substitute for the page copy inside the app?
- Why does the billing page talk about trial limitations so directly?
- What if I only need the lens catalog and documentation, not live generation yet?
- Why does 7DEA keep telling me to start with Universal?
- What is the difference between a deliverable and an export?
- If I cancel a trial, do I lose access instantly?
- What is the role of context help if Aegis is already available?
- Why are some account actions asking for stronger confirmation?
- Do I need a paid plan to understand what 7DEA will do for my team?
- How do I know whether a locked state is normal or a bug?
- What should I do if dashboard and billing do not seem to agree?
- Can I use Start Here as a training page for teammates?
- What makes a deliverable review healthy?
- How should I think about trial if procurement approval comes later?
- Is a share link the same as making something public forever?
- What should I do if I have a Final deliverable but want to improve the framing anyway?
- How technical do I need to be to benefit from the trust bar?
- What if my first draft feels too broad?
- Why is the docs route worth reading if the app already has context help?
- What if I only need one good baseline artifact, not a large operating program?
- When a Temporary Wait State Is Normal
- When to Stop Self-Diagnosing
Glossary
A practical glossary of the product terms, states, and concepts that appear most often in live use.
- Entitlement
- Aegis
- Aegis action surface
- Aegis chat surface
- Aegis fallback
- Aegis live guidance
- Anchor
- Analysis execution
- App route
- Assumptions and limits
- Audit history
- Audit Pack ZIP
- Audit-ready
- Authenticated startup walkthrough
- Baseline
- Billing portal
- Build identifier
- Cancel trial
- Cancellation scheduled
- Catalog version
- Certified output
- Checkout
- Commercial coherence
- Context help
- Controlled distribution
- Current page context
- Customer-facing manual
- Data export
- Data rights
- Decision support
- Deterministic draft
- Divergence
- Download PDF
- Draft
- Entitled user
- Entitlement
- Explorer
- Evidence trail
- FAQ
- Feature lock
- Final
- Final PDF
- First-time checklist
- First-session quickstart
- Guided onboarding
- Human review
- Intent phrase
- Jurisdiction overlay
- Lens
- Lens catalog
- Lens family
- Lens selection
- Live guidance
- llm_fallback
- llm_live
- Membership invitation
- Multi-lens comparison
- Non-entitled state
- Onboarding path to draft creation
- OTP
- Page context
- Paid membership
- Past due
- Pilot
- Plan context
- Plan overview
- Processing window
- Profile
- Queued
- Renewal
- Re-auth
- Revocable share link
- RPIM
- Scope statement
- Security session
- Session required
- Share or revoke share
- Signal sync
- Start Here
- Status-tracked
- Structured assistance
- Subscription active
- System mode
- Team seat
- Token status
- Trial
- Trial day counter
- Trial limitations
- Trust bar
- Universal
- Uptime
- Version changes
- What this page does
- Windowed
- Workflow gate
- Baseline-first strategy
- Build identifier
- Checklist completion
- Commercial invitation
- Controlled capability
- Docs route
- Evaluation workflow
- Fast path
- First deliverable posture
- Freshness posture
- Governance window
- Help-map anchor
- Interpretation layer
- Operational fit
- Page owner
- Payment-method verification
- Plan fit
- Procurement posture
- Public-safe documentation
- Review cadence
- Route sequence
- Session refresh
- Share readiness
- State mismatch
- Support packet
- Team workflow
- Trial invitation path
- Usage posture
Working Sessions and Review Routines
How to structure evaluation, trial, creation, review, and distribution sessions so the product stays legible under real working pressure.
- What a good session is trying to achieve
- Session type 1: Evaluation and orientation
- Session type 2: Trial validation
- Session type 3: First-draft creation sprint
- Session type 4: Internal review meeting
- Session type 5: Distribution and handoff meeting
- Running the session so the product stays legible
- Session notes and durable memory
- When a session should stop
Communicating Results to Stakeholders
How to frame Draft and Final artifacts responsibly for executives, reviewers, operators, clients, and partners.
- Start with audience, not with attachment
- Communicating with executives and budget owners
- Communicating with legal, compliance, or risk reviewers
- Communicating with operators and implementation teams
- Communicating with clients, partners, and external stakeholders
- Communicating the meaning of Draft and Final
- Writing effective one-paragraph summaries
- What not to say
- Turning communication into repeatable practice
Commercial Evaluation and Procurement Readiness
How to turn trial evidence into buying evidence and evaluate the paid plans with operational discipline.
- What a serious evaluation should answer
- Translating trial evidence into buying evidence
- Choosing a paid plan with discipline
- Procurement conversations that go better
- What budget owners usually need to hear
- Signals of genuine readiness to buy
- Signals that the team should keep evaluating
- Building the business case without exaggeration
Long-Term Adoption and Change Discipline
How to keep local training, team memory, and live product truth aligned as the platform evolves.
Public Support Expectations and Service Boundaries
How the public product, manual, Aegis, and support each contribute to a trustworthy user experience without blurring their roles.
New to 7DEA? Start with Getting Started. Need the commercial model first? Go to Plans, Trials, and Entitlements.