Section 2 Plans
Keep the current plan cards, public-safe specs, AWA LLM access levels, BYO agent harness, and responsive fit.
AWA by Accware
Only Section 2 is validated.
This is the public render library for the production rebuild. Section 2 Plans is the only validated direction. Every other section is invalidated or deferred until a new operator-approved direction exists. Images remain references only: final copy, logo, routes, animations, accessibility, and responsive behavior must be rebuilt in deterministic HTML/CSS.
Validation board
One validated section. Everything else is open.
This board is the handoff for the next implementation worker. Section 2 is approved. Sections 1, 3, 4, 5, 6, 7, and 9 are invalidated. Section 8 is deferred until a real system screenshot is available.
Sections 1, 3, 4, 5, 6, 7, 9
Use their images only as partial references. They are not approved as final visual, motion, or implementation directions.
Section 8 Memory
Do not implement or regenerate it yet. Wait for an actual screenshot of the real system before designing the memory graph.
01 Invalidated
Welcome
Historical framing only. Rebuild after Section 2 quality bar with exact header, no form, and deterministic AWA workspace UI.
02 Validated
Plans
Current accepted baseline. Preserve the plan copy, public specs, AWA LLM access levels, BYO agent harness, Pro distinction, and responsive fit.
03 Invalidated
Automation Carousel
Needs eight distinct product scenes, not a generic carousel template. Email, Sales, Calls, WhatsApp, Browser, Files, Coding, and Ops each need a real workflow.
04 Invalidated, useful
Private Workspace
Good inspiration, but upgrade it: clearer convergence, stronger premium product surface, less dashboard language, and better device-to-workspace story.
05 Invalidated
AWA Intelligence
Direction only. Must become more minimalist, less render-heavy, and much stronger on the right-side AWA Intelligence product mechanism.
06 Invalidated
Token Optimization
Too unclear. Rebuild the right side as a coordinated dispatch tree with Fable 5, GPT 5.6 Solana, GPT 5.6 Tera, Luna, AWA Intelligence, and AWA Pinocchio verifier harness.
07 Invalidated, usable idea
Pinocchio Verification
Keep the theater idea, but replace orange/static proof dots with a real simulated verification run: cursor moves, evidence appears, badge lights after proof.
08 Deferred
Memory Map
Do not build yet. Wait for an actual screenshot of the real system, then design the Obsidian-like memory graph from that evidence.
09 Invalidated
Final Section
Do not repeat pricing cards. Section 2 already owns plans. Find a fresh activation/account handoff concept before implementation.
Section 3 render lock
Automation carousel candidates with one shared shell.
These eight renders are implementation references for the Section 3 carousel. They use the updated operator order: Email, Coding, Sales, Calls, WhatsApp, Browser, Files, Ops. They are not final HTML/CSS acceptance; deterministic implementation must rebuild labels, copy, motion, accessibility, and responsive behavior.
03 Email
Email workflow
Intake, private-memory draft, verification, approval, reply sent, follow-up, and memory saved.
03 Coding
Coding workflow
Orchestrator, specialist agents, code diff, tests, browser verification, Pinocchio review, human handoff, and memory.
03 Sales
AW-Sales loop
Fetcher, Reacher, and Closer across discovery, enrichment, outreach, objections, approval, and handoff report.
03 Calls
Call operation
Brief, place or answer call, transcribe, extract commitments, approval handoff, follow-up, and memory.
03 WhatsApp
Private chat handling
Customer chat, workspace context, draft and approval, status summary, activity ledger, and memory saved.
03 Browser
Browser automation
Book a holiday through private browser research, comparison, verification, approval gate, and trip memory.
03 Files
Private file work
File tree, document preview, comparison, summary, organized suggestions, approval before edits, and memory.
03 Ops
Recurring operations
Schedules, monitors, daily brief, incident queue, approval gate, report sent, and operational memory.
Reference stack
Historical stitched stack, not approval.
This stack remains useful for broad rhythm only. It is not a validated production target except for Section 2. Do not use it to claim Sections 1, 3, 4, 5, 6, 7, 8, or 9 are accepted.
Lab
Rejected or secondary renders that still teach the implementation.
The lab is not the production target. Use it only for specific strengths called out here: scene density, mobile simplification, access meters, tree spacing, or proof ledger behavior.
02 Lab B
Hardware shelf identity
Useful product depth. Do not copy generated copy or traffic emphasis.
02 Lab C
Comparison discipline
Useful for exact plan comparison and responsive table thinking.
02 Lab D
Capacity rhythm
Borrow left-side identity and benefit rhythm, not layout complexity.
03 Lab B
Browser panel density
Use for Browser mode: tabs, table extraction, form run, verified result.
03 Lab C
Sales path
Use for prospect research, objections, outreach, CRM, follow-up sequence.
03 Lab D
Coding/Ops proof
Use for code changes, tests, CI/deploy, verifier proof, scheduled monitor.
04 Lab B
Device bridge
Good continuity concept, but generated app-logo fragments are too literal.
04 Lab C
Before/after split
Clear transformation, but too crowded for the final selected direction.
04 Lab D
Workspace module density
Use for central module detail if Section 4 feels too sparse.
05 Invalidated lab A
Proof lane clarity
Only borrow proof-path structure. The final section needs a quieter, more credible AWA Intelligence mechanism.
05 Invalidated lab B
Task pipeline
Access-meter idea only. Do not copy the render-heavy composition or weak right-side product object.
05 Invalidated lab C
Access matrix
Use only for plan-access clarity. Correct all generated policy/spec text and redesign the visual language.
05A Candidate 1
Intelligence core
Dark global field that positions AWA Intelligence as the centre of company context, priorities, specialist work, and approval.
05A Candidate 2
Signal to action
Dark global field showing customer, sales, operational, and project signals converging into a reviewable operating plan.
06 Invalidated lab B
Tree spacing
Borrow only the readable tree spacing. Rebuild labels around Fable 5, GPT 5.6 Solana, GPT 5.6 Tera, Luna, and AWA Intelligence.
06 Invalidated lab C
Sankey comparison
Token-flow metaphor only. The accepted direction must be a clear coordinated dispatch tree, not an abstract diagram.
06 Invalidated lab D
Iteration contrast
Borrow the strong `10-20 manual iterations` versus `1 orchestrated run` claim. Rebuild the model and verifier lanes.
07 Invalidated lab A
Classic theater
Proof sequence only. Final motion must show a real cursor-driven verification run, not static markers.
07 Invalidated lab B
Evidence queue
Evidence queue concept only. Avoid clutter and make each proof state visibly earned.
07 Invalidated lab D
Proof ledger
Use for mobile simplification and ordered proof badges after the desktop verification animation is solved.
08 Deferred lab B
Floating detail drawer
Do not implement yet. Revisit only after an actual real-system screenshot exists.
08 Deferred lab C
Cluster labels
Do not use as approval. Future graph must follow the real system screenshot and Obsidian-like interaction.
08 Deferred lab D
Recent memory timeline
Optional idea only after the real graph direction is approved.
09 Invalidated lab A
Classic close
Do not repeat plan cards or pricing. Use only if it helps a fresh activation/account handoff story.
09 Invalidated lab B
Activation journey
Journey object is the only useful idea. The next concept must avoid Section 2 duplication.
09 Invalidated lab C
Closing stack
Hierarchy reference only. Rebuild around activation, sign-in, and account handoff without pricing clutter.
Implementation contract
Translate the renders, do not copy their mistakes.
Generated PNGs frequently contain wrong microcopy. The live site must follow `AWA_LANDING_VISUAL_LOCK.md` and `AWA_LANDING_AUTONOMY_EXECUTION.md` for final language, routes, specs, and behavior.
HTML/CSS text only.
Use exact product copy in source. Never trust generated text pixels for specs, plan policy, routes, or claims.
Real surfaces, not decoration.
Every section needs a believable product object: workspace, carousel, switchboard, token tree, verifier, memory graph, activation console.
Animation explains truth.
Animate routing, consolidation, proof, memory selection, token counts, and activation. Do not add idle technical noise.
No-slop gate
Anything that violates these rules fails.
- No generated logo errors, malformed text, fake UI labels, fake browser chrome, or unreadable embedded copy inside production HTML.
- No hero account form, no AWA Voice nav, no public `gateway` hero wording, and no internal VPS names in public UI.
- No generic SaaS dashboard cards, fake terminal filler, decorative grids, blobs, orbit diagrams, or filler product panels.
- No overlap, clipping, horizontal overflow, accidental hidden content, or fixed-size dead layout on large or mobile screens.
- Every visual must explain product truth: privacy, orchestration, verification, memory, automation, workspace ownership, or token efficiency.
- Before deploy, capture and inspect desktop, large desktop, tablet, and mobile screenshots. Any visible defect blocks publish.