Chapter 13: Frequently Asked Questions

This chapter answers the recurring questions that appear once users have already begun to understand the route model. These are not marketing questions. They are the questions people ask when they are trying to use the product correctly and want the shortest trustworthy explanation.

I can browse the lens catalog without signing in. Why can’t I generate a deliverable from the same surface?

Catalog browsing is intentionally open because 7DEA wants users to understand the framework landscape before they commit to a plan or a workflow. Generation is different because it consumes account-scoped capability and produces governed output. The correct interpretation is not that the catalog is broken; it is that browsing and execution are separate capability categories. Use the catalog to narrow the right baseline and overlays, then sign in and activate the appropriate plan before you expect execution actions to proceed.

Why does Aegis sometimes answer with a membership invitation instead of route-specific live guidance?

That behavior means the account is in an explorer or otherwise non-entitled state for live paid guidance. The fallback is deliberate and user-facing: it explains that live guidance activates with an active trial or paid plan. The right next step is to verify sign-in and billing state rather than trying to rephrase the same prompt repeatedly.

What is the safest first deliverable strategy for a new user?

Use the Universal baseline first, include a concrete deployment description, name the intended users, describe the operating jurisdictions, and mention any obvious high-risk or regulated context. That approach keeps the first draft broad enough to be useful while giving the system enough specificity to avoid generic output.

Why is my deliverable still Draft even though the creation step succeeded?

Draft and creation success are not contradictions. The product intentionally creates a deterministic draft first so you can review scope immediately. Final publication, including the PDF, can occur later during a governed processing window. Treat Draft as an invitation to review the substance and Final as the later publication milestone.

Can trial users use Aegis live guidance?

Yes. In the current commercial model, active trial users are entitled to live Aegis guidance. Trial users should still expect some export and sharing actions to remain locked until a paid plan is active.

Why do some buttons say locked even after I signed in?

Sign-in confirms identity; it does not automatically unlock every commercial or processing capability. A lock after sign-in usually means the action depends on plan entitlement, trial limitations, a re-auth token, or Final deliverable state. Always read the nearby explanation text because that wording tells you which of those categories is actually responsible.

What should I send support when something feels inconsistent?

Send the route you were on, the exact UI wording, the time you saw it, the rough action sequence that produced it, and whether the account was explorer, trial, or paid at the time. Support works fastest when the report is state-focused and chronological instead of interpretive.

How should I think about the difference between the dashboard and Start Here?

Dashboard is the signed-in command surface for current state, next steps, and recent work. Start Here is the short instructional runway for people who want the fastest route to a first result. If you are already signed in, dashboard usually gives better runtime truth. If you are still orienting, Start Here is often the calmer place to learn the workflow.

It means some publication-sensitive actions are governed by allowed windows rather than being finalized at any instant. Most users do not need the internal scheduling details. What matters is that Draft creation can still happen immediately while Final publication may wait for the next allowed window.

The safe assumption is no. Sharing is a controlled distribution action tied to finalization and entitlement. If the route shows a locked or disabled share state, treat that as authoritative and wait until the deliverable is Final and the plan allows sharing.

Is the manual a substitute for the page copy inside the app?

No. The manual exists to interpret live product truth, not override it. The fastest and safest method is to read the page copy, then use the manual to understand why that page says what it says and what the next action should be.

Why does the billing page talk about trial limitations so directly?

Because commercial clarity is part of trust. 7DEA surfaces the exact differences between trial and paid behavior on the billing page so users know what will unlock, what remains locked, and what will happen if they choose to continue or cancel.

What if I only need the lens catalog and documentation, not live generation yet?

That is a valid early-stage workflow. Many users first browse the lens catalog, read the manual, and clarify their jurisdictions and operating model before they activate a trial or plan. The public surfaces are designed to support that learning phase safely.

Why does 7DEA keep telling me to start with Universal?

Because Universal is the best baseline for most real organizations. It gives a stable governance starting point that helps later overlays make more sense. Starting with too many overlays too early can create noise instead of clarity.

What is the difference between a deliverable and an export?

A deliverable is the structured working output in the app. An export is one way of packaging or distributing that output, such as a PDF or audit pack. Users often confuse the two and assume export problems mean the deliverable itself failed, but those are separate layers.

If I cancel a trial, do I lose access instantly?

Cancellation language usually means the account will stop auto-converting or renewing at the end of the current period. The exact wording on the billing page is the runtime truth. Read it carefully before assuming immediate loss of access.

What is the role of context help if Aegis is already available?

Context help is the stable documentation layer, while Aegis is the interactive explanation layer. Context help is better when you want the canonical written reference. Aegis is better when you want route-aware interpretation or a guided next step in the moment.

Why are some account actions asking for stronger confirmation?

Sensitive account changes have a higher trust threshold because they affect privacy, billing, or security posture. Re-auth is the product’s way of ensuring that a currently signed-in session is still under the control of the intended user at the moment of the sensitive action.

Do I need a paid plan to understand what 7DEA will do for my team?

No. The public site, docs, lens catalog, and trial invitation path are all part of the education layer. The goal is that you can understand the product shape, choose the right lens posture, and evaluate fit before committing to a plan.

How do I know whether a locked state is normal or a bug?

A normal lock usually comes with plain-language explanation that aligns with your account state, deliverable state, or trial limitations. A likely bug is when the wording and the visible state disagree, or when one part of the app claims a capability is unlocked while the action still behaves as though it were locked.

What should I do if dashboard and billing do not seem to agree?

Refresh both routes and read the visible wording again in order. If the mismatch remains visible, capture both views and the route sequence that led there. That is a stronger signal of a real state contradiction than either route taken in isolation.

Can I use Start Here as a training page for teammates?

Yes. Start Here is one of the best routes for a short guided introduction because it explains the fast path without assuming deep prior knowledge. Pair it with the relevant docs anchors so the teammate can move from summary to detail when needed.

What makes a deliverable review healthy?

A healthy review confirms scope, lens posture, current state, assumptions, and next actions before debating finer wording. In other words, reviewers should first agree on what the artifact is and what state it is in before they argue about what it ought to say.

How should I think about trial if procurement approval comes later?

Use trial to test the workflow and artifact quality, not to imitate every enterprise process. The goal is to gather grounded evidence about usefulness, route clarity, and live guidance value so later procurement conversations rest on real experience rather than speculation.

No. Share links in 7DEA are designed for controlled distribution and revocation. Their existence is part of the product’s trust posture: the platform supports circulation, but it also makes reversal and governance possible.

What should I do if I have a Final deliverable but want to improve the framing anyway?

Treat Final as the current publication state, not as the end of learning. Use the finished artifact to refine the next scope statement, lens set, or review sequence. Strong teams improve their next run from what the current final artifact taught them.

How technical do I need to be to benefit from the trust bar?

Not very. The trust bar is designed for interpretation, not for engineering operations. You mainly need to know that it summarizes current runtime posture in a way that helps explain timing, billing behavior, and reproducibility.

What if my first draft feels too broad?

First confirm whether the scope statement itself was broad. If it was, refine the description before assuming the lens set failed. If the scope is already specific, then consider whether an additional overlay or a different reviewer conversation is the better next step.

Why is the docs route worth reading if the app already has context help?

Context help is the guided index. The docs route is the deeper explanation. They are strongest together: context help gets you to the right anchor, and the manual gives you the fuller reasoning and workflow logic behind the page you are using.

What if I only need one good baseline artifact, not a large operating program?

That is a valid use case. The manual emphasizes baseline-first work precisely because many teams need one clear, reviewable starting artifact before deciding whether to scale usage into a larger recurring governance program.

When a Temporary Wait State Is Normal

A temporary wait is normal when the product is clearly telling you a later publication step depends on a processing window or when the current action is still waiting for Finalization. A temporary wait is not normal when the billing page says the account is active, the deliverable says Final, and the route still behaves as though neither were true. That kind of mismatch is exactly what the troubleshooting workflow is designed to expose.

When to Stop Self-Diagnosing

Stop self-diagnosing when you have captured clear evidence of state mismatch, when a sensitive account action behaves in a way the page itself cannot explain, or when route transitions leave you in a contradictory state you can reproduce. At that point more clicking usually creates noise instead of clarity. Capture the evidence and escalate.