{% extends 'base.html' %}
{% block heading %}Final Project Plan & Scope<script src="{{url_for('static',filename='js/report.js')}}" defer></script>
{% endblock %}
{% block content %}
{% include '_project_bar.html' %}
<section class="hero final-hero"><div><span class="kicker">WIZE FINAL REPORT</span><h2>{{project.name if project else 'Select or create a project'}}</h2><p>{{project.description if project and project.description else 'This report turns the Wize strategy questions, connected Whys, PERT estimates, tasks, team structure, assumptions and handbook guidance into one execution plan.'}}</p><div class="actions"><button type="button" class="ghost" id="print-plan">Print / Save PDF</button><a class="ghost" href="{{url_for('handbook')}}">Read Strategy Handbook</a><a class="ghost" href="{{url_for('learn')}}">Review lessons</a><a class="primary" href="{{url_for('wizard')}}">Update strategy</a></div></div><div class="score"><span>Plan readiness</span><strong>{{readiness_pct}}%</strong><small>Complete the missing gates below before treating the plan as final.</small></div></section>
<section class="panel"><span class="kicker">0 · READINESS GATES</span><h2>What is still missing?</h2><p>A person who does not know what to do should be able to use this list as the immediate checklist. Green items are already supported by project data; incomplete items tell you exactly where to go next.</p><div class="readiness-grid">{% for label,ok,detail in readiness_items %}<div class="readiness-card {{'ready' if ok else 'not-ready'}}"><b>{{'✓' if ok else '→'}} {{label}}</b><span>{{detail}}</span></div>{% endfor %}</div></section>

<section class="panel"><span class="kicker">1 · EXECUTIVE PURPOSE</span><h2>What are we trying to accomplish?</h2><p><b>Project:</b> {{project.name if project else 'Not defined'}}</p><p><b>Project description / decision context:</b> {{project.description if project and project.description else 'Not defined yet. Add a short description so someone reading the plan understands the situation.'}}</p><div class="callout"><b>How to use this section:</b> The description should explain the situation, not merely repeat a task. The five Need Goals below define the concrete scope.</div></section>

<section class="panel"><span class="kicker">2 · STRATEGIC SCOPE</span><h2>The five questions define what is in scope</h2><p>Each <b>Need</b> is a concrete Goal. Wish, Dream and Fantasy are the connected reasons that explain why that Goal matters. A reader should be able to trace each Goal upward without guessing.</p>
<div class="strategy-question-grid">{% for g in goals %}<article class="question-chain panel-inner"><span class="kicker">{{g.category}}</span><h3>Goal / Need</h3><p class="scope-goal">I need to <b>{{g.need}}</b> so that I can <b>{{g.so_that}}</b>{% if g.because %} because {{g.because}}{% endif %}.</p><div class="mini-chain">{% for r in strategy_rows if r.category==g.category and r.level!='Need' %}<span>WHY? ↓</span><div><b>{{r.level}}{% if r.level=='Wish' %} / Why 1{% elif r.level=='Dream' %} / Why 2{% elif r.level=='Fantasy' %} / Why 3{% endif %}</b><p>I need to {{r.need}} so that I can {{r.so_that}}{% if r.because %} because {{r.because}}{% endif %}.</p></div>{% endfor %}</div></article>{% else %}<p>No Need Goals yet. Start with Strategy + Whys.</p>{% endfor %}</div>
<div class="callout"><b>Scope rule:</b> Work that does not support one of these Need Goals should be challenged before it enters the plan. Porter-style strategy requires trade-offs—what the project will <em>not</em> do should be made explicit when competing work appears.</div></section>

<section class="panel"><span class="kicker">3 · TIME / STRESS SCOPE</span><h2>PERT assessment for each Goal</h2><p><b>Program Evaluation and Review Technique (PERT)</b> turns Best / Most Likely / Worst estimates into a weighted planning view. Wize adds a stress range so uncertainty is visible instead of hidden.</p><table><thead><tr><th>Strategic question</th><th>Goal</th><th>Status</th><th>Expected</th><th>Standard deviation</th><th>Wize stress range</th></tr></thead><tbody>{% for g in goals %}<tr><td>{{g.category}}</td><td>I need to {{g.need}} so that I can {{g.so_that}}</td><td>{% if g.expected is not none %}<b>ASSESSED</b>{% else %}<b>NEEDS PERT</b>{% endif %}</td><td>{% if g.expected is not none %}{{'%.2f'|format(g.expected)}} {{g.unit}}{% else %}—{% endif %}</td><td>{% if g.sigma is not none %}{{'%.2f'|format(g.sigma)}}{% else %}—{% endif %}</td><td>{% if g.expected is not none %}{{'%.2f'|format(g.high_stress)}} → {{'%.2f'|format(g.low_stress)}} {{g.unit}}{% else %}<a href="{{url_for('pert_original')}}">Run PERT</a>{% endif %}</td></tr>{% else %}<tr><td colspan="6">No Need Goals yet.</td></tr>{% endfor %}</tbody></table></section>

<section class="panel"><span class="kicker">4 · EXECUTION PLAN</span><h2>What to do</h2><p>These are the executable records generated from the Wize strategy process. Work from highest priority downward, but keep asking whether each task still supports a Need Goal.</p><table><thead><tr><th>Priority</th><th>Status</th><th>Source</th><th>Action / reason</th></tr></thead><tbody>{% for t in tasks %}<tr><td>{{t.priority}}</td><td>{{t.status}}</td><td>{{t.source_level or 'Task'}}</td><td>{% if t.need and t.so_that %}I need to {{t.need}} so that I can {{t.so_that}}{% if t.because %} because {{t.because}}{% endif %}{% else %}{{t.title}}{% endif %}</td></tr>{% else %}<tr><td colspan="4">No execution tasks yet.</td></tr>{% endfor %}</tbody></table><div class="callout"><b>Operations tip:</b> If the team is busy but output is not moving, use the handbook's Theory of Constraints question: <em>What single bottleneck limits the whole system?</em> Improve the constraint before optimizing non-constraints.</div></section>

<section class="panel report-section"><span class="kicker">5 · TEAM / MANAGEMENT SCOPE</span><h2>Who coordinates the work?</h2><p>The latest team design gives each working group real management, a Product Lead for delivery, and stable contributor pairs so communication is reduced without becoming a one-person hub.</p>{% if comms %}{% set r=comms[0] %}<div class="report-summary-row"><div><b>{{r.people}}</b><span>People</span></div><div><b>{{r.local_managers}}</b><span>Managers</span></div><div><b>{{r.product_leaders}}</b><span>Product Leads</span></div><div><b>{{r.stable_pair_channels}}</b><span>Stable peer pairs</span></div><div><b>{{r.channels}} → {{r.structured}}</b><span>Communication lines</span></div><div><b>{{'%.1f'|format(r.reduction_pct)}}%</b><span>Reduction</span></div></div><p>{{r.sentence}}</p>{% if comms|length > 1 %}<details class="quiet-details"><summary>Show {{comms|length - 1}} older team calculation{{'' if comms|length==2 else 's'}}</summary><div class="detail-body">{% for old in comms[1:] %}<p><b>{{old.people}} people:</b> {{old.local_managers}} Manager(s), {{old.product_leaders}} Product Lead(s), {{old.stable_pair_channels}} stable pair line(s), {{old.channels}} → {{old.structured}} channels.</p>{% endfor %}</div></details>{% endif %}{% else %}<p>No communication design logged. Run Communications after you know how many people will execute the Goals.</p>{% endif %}<div class="callout"><b>7-S reminder:</b> Structure is only one part of execution. Check whether systems, skills, staff, style and shared values support the strategy too.</div></section>

<section class="two-col"><div class="panel"><span class="kicker">6 · ASSUMPTIONS / EVIDENCE</span><h2>Clay Tablets</h2><p>These are the assumptions and reasons that should survive beyond a single task. Challenge them when evidence changes.</p>{% for x in clay %}<div class="journal-entry"><p>{{x.text}}</p></div>{% else %}<p>No assumptions captured yet. Add the assumptions that would cause the plan to fail if they are wrong.</p>{% endfor %}</div><div class="panel"><span class="kicker">7 · LEARNING LOG</span><h2>Recent journal evidence</h2><p>Use this to compare what the plan expected with what actually happened.</p>{% for x in journal %}<div class="journal-entry"><small>{{x.created_at}}</small><p>{{x.body}}</p></div>{% else %}<p>No journal entries yet. Record observations during execution.</p>{% endfor %}</div></section>

<section class="panel"><span class="kicker">8 · HANDBOOK DECISION CHECKS</span><h2>Tips to consider before you approve the plan</h2><p>These are not automatic conclusions. They are review questions derived from the Strategy Handbook so the final plan does not stop at the first framework or metric.</p><div class="tip-grid">{% for t in final_tips %}<div class="tip-card"><b>{{loop.index}}. {{t.title}}</b><p>{{t.tip}}</p></div>{% endfor %}</div></section>

<section class="panel"><span class="kicker">9 · FINAL GO / NOT-YET DECISION</span><h2>{{'Execution-ready candidate' if readiness_pct==100 else 'Not final yet — finish the missing gates'}}</h2>{% if readiness_pct==100 %}<p>All Wize readiness gates currently have supporting records. Before committing, read the handbook decision checks above and confirm the assumptions are still valid. Then execute tasks, journal what actually happens, and rerun the strategy cycle when conditions change.</p>{% else %}<p>Use the Readiness Gates at the top as the next-action list. Wize should not pretend the project plan is complete while key strategy, PERT, execution, communication or assumption records are still missing.</p>{% endif %}<div class="actions"><a class="primary" href="{{url_for('tasks')}}">Go to execution tasks →</a><a class="ghost" href="{{url_for('clay_tablets')}}">Challenge assumptions</a><a class="ghost" href="{{url_for('journal')}}">Record learning</a></div></section>
<script src="{{url_for('static',filename='js/report.js')}}" defer></script>
{% endblock %}