Changelog

• –Project deployed to Cloudflare Pages at nws-360.pages.dev. Auto-deploys from GitHub on push to main.

• –New file — landing page with card-based navigation to all project documents. Categories: Planning & Management, Internal Resources, Client-Facing, Service References.

• –Added data-editable contenteditable system to index.html and Project-Master-NWS-360.html. Edit button activates inline text editing; Update button (double-click to confirm) saves changes to disk via File System Access API with .bak backup; Cancel reverts all changes.
• –Edit mode only available on localhost — hidden on Cloudflare Pages and all remote hosts. Edits must originate locally and sync via source control.
• –Root cause of save failures: confirm() dialog blocked JS execution while Live Server reloaded the page, killing the async write. Fixed by replacing confirm() with inline double-click confirmation and writing the file before the .bak backup.

• –D:\tools\start-360.bat — launches npx live-server on port 5500 with auto-reload. Alternative to VS Code Live Server extension; no IDE required.
• –stop-360.bat — kills the dev server process.

• –Renamed file and updated all references across index.html, Project-Master-NWS-360.html, changelog.html, and .claude/agents/paul.md.

• –All HTML files now have a clickable NWS-360 logo/label linking back to index.html. BlueBlock pages use the product-label badge; topbar pages wrap the brand text or logo image in an anchor.

• –New file — draft deliverable specs for 1:1 meetings with each service owner. 5 pre-filled assessments: SEO Health (Alex), Accessibility (Sydney), Security (Eric), GA4 (Fred), Uptime (Greg).
• –Each assessment includes: draft tier table (S/M/L/XL), KPI with BDM talking point, and tailored questions covering scope validation, agentic feasibility, human vs. agent split, effort/timeline estimates, and tooling.

• –New file — central index of all project files organized by category: Planning & Strategy, Service Pages, Assessments, Portal Prototypes, Sales & Marketing, Project Tracking. Data files summarized as a group.
• –Each file entry has a clickable link, brief description, and last-updated date. Will be updated whenever .html, .xlsx, or .md files are created or modified.

• –Fundamental shift: Phase 1 is no longer “build skill sheets from a template.” It is now: draft deliverable specs per service → meet 1:1 with each owner → capture capacity, agentic feasibility, help needed, and timeline → then build skill sheets and set pricing from those conversations.
• –Each person needs to assess whether an agentic version of their service is feasible, what the human/agent mix looks like, and what help they need. Team members are at varying levels of agentic competence.

• –Deferred: pricing-baseline — pricing will emerge from per-service effort estimates, not a top-down decision. Not a Phase 1 blocker.
• –Deferred: retainer-hours-fixed — need to understand deliverables and effort before setting hours. Not a Phase 1 blocker.
• –New: per-person-service-assessment — critical path for Phase 1. Each owner must validate deliverables, estimate effort, and assess agentic feasibility.
• –Clarification: Meridian proposal is a fake client for internal discussion only, not a real prospect. Subject to revision.

• –Priority focus changed from structure-first to phase1-blockers. Paul now triages everything against “does this block the first client?”
• –5 concrete outputs defined: status check, blocker triage, next-action list, decision prompts with options, skill sheet production queue.
• –New rules: track changes since last invocation, don’t re-ask resolved questions, be concrete about actions.

• –Expanded team roster from 13 placeholder entries (mostly TBD) to 35 named people across all departments: Account Directors (JJ, Dana, Brett), SEO/Digital Marketing (Alex, Ed K, Rachel, Trevor, Ramie), UX/Content (Jenna, Katelyn, Mugsie), Front-end (Sydney, Marshall), Back-end (Greg, Eric, Jon, Gerry, Angela, Aaron, Chad, Justin, Amanda, Dylan), Analytics (Fred), IT (Diamond, Brian), BDMs (Rick, Jim, Matt, Hayden, Tim), Management (CeCe, Ed A).
• –Each entry includes role, service assignments, human skills, and agent IDs where applicable.

• –Primary owners set for 15 of 18 existing services. Remaining 3 (CWV, Competitive Benchmarking, Proactive Optimizations) left TBD pending category decision.
• –New service: Content Security Policy (CSP) — owner: Greg. Category: technical. Quarterly cadence.
• –New service: Digital Marketing Strategy — owner: Ed K. Category: growth. Monthly cadence.

• –All ownerId fields updated from tbd-* placeholders to actual person IDs. Two new skill sheet entries added for CSP and Digital Marketing.
• –Agent owner references updated: accessibility-scanner → Sydney, seo-scanner → Alex, cwv-scanner → Sydney, ga4-scanner → Fred, 404-scanner → Dylan, security-scanner → Eric, uptime-monitor → Greg.

• –portal/dashboard.html line 908: “Account Manager” → “Account Director”
• –NWS-360_Team_Branded.html lines 730–733: Merged “Account Manager” + “Project Manager” into single “Account Director” bench item (these are the same role at Northwoods).
• –estimating.md line 145: Core team updated to “Account Director (AD), SEO Specialist, Front-end Dev, Back-end Dev”

• –Resolved: skill-sheet-owners — all owners assigned (3 services still TBD pending category decision).
• –New OQ: Should the bench grid in NWS-360_Team_Branded.html show actual person names instead of generic role labels?
• –New OQ: What category should CWV, Competitive Benchmarking, and Proactive Optimizations fall under? Patrick mentioned “baseline benchmarking” but needs to finalize.

• –All assignments driven by person-roles.md created by Patrick.

• –New data file with 6 cross-service KPIs (conversion rate, organic traffic, form submissions, keyword rankings, bounce rate, Lighthouse score) — the business outcomes clients actually care about.
• –19 per-service KPIs each with: primary KPI + unit, goal, baseline capture checklist, measurement source, reporting cadence, ROI narrative, and BDM talking point for sales conversations.
• –Framework: baseline → agreed target → monthly delta. Baseline assessment is now both a deliverable and a contract anchor.

• –New “ROI Framework” section added to sidebar and main content. Cross-service KPI card grid at top; full per-service KPI table below with goals and BDM talking points.

• –roiId field added to all 19 services, linking each to its ROI metrics entry.
• –4 new open questions: who selects KPIs at kickoff, how to get GA4/Search Console access for baseline, what the monthly ROI report looks like, and whether targets are set at kickoff or after 90 days of actuals.

• –Created ProjectVision.html — central project hub with 11 sections: Product Overview, Two Portals, Service Catalog, Pricing Framework, Team & Ownership, Skill Sheet Tracker, Agent Development, YouTube/Blog Topics, Phase Gates, Open Questions, Project Files.
• –All content loads from 7 separate data/*.js files (no server required — file:// compatible). Edit any data file and reload to update the plan.
• –Data files: services.js (19 services with S/M/L/XL tier pricing), team.js, agents.js, skill-sheets.js, content.js, milestones.js, open-questions.js.
• –Four phase gates defined targeting Q2 first customer: Phase 1 Sales Enablement, Phase 2 AD Portal, Phase 3 Client Portal, Phase 4 Marketing Funnel.
• –12 YouTube/blog topic seeds added. 10 open questions documented with owners and build impact.

• –Created estimating.md — 26 scope line items, pricing variables, and 10 open questions formatted for sharing with Claude.ai.
• –Created BUILD_BRIEF.html (Paul’s build brief) — all 5 planning open questions resolved, terminology corrections, schema definitions, and prioritized build order.

• –Company name corrected to Northwoods (not “Northwoods Digital”) across all memory files and new deliverables.
• –Standardized team terminology: AD (Account Director) replaces “Account Manager” / “Project Manager”; BDM (Business Development Manager) replaces “sales team”.
• –Two-portal architecture defined: Client Portal (external, magic link) and AD Portal (internal, VPN-only, deliverable checklist + hours tracker, syncs to client portal).

• – All 67 font-size values scaled up 20% across the dashboard. Range: 9px → 11px (smallest labels) through 36px → 43px (largest score displays). Layout dimensions (padding, widths, heights) left unchanged. Going forward, new dashboard/portal UI pages will use a 16px base font rather than 13px.

• – Created portal/dashboard.html — full NWS-360 client portal dashboard. Fixed sidebar navigation with scroll-aware active states, sticky topbar with client/site selector, and modular card layout across all service areas. Mock data based on a fictional “Meridian Health Systems” client. Sections: overall health score strip, Core Web Vitals (CWV gauges), SEO health, Privacy/CMP (with compliance level track), Accessibility, Security, Uptime (generated bar chart), Analytics/GA4, Site Baseline Inventory, and AI-generated recommendations.

• – Created services/cmp-privacy-consent.html — the first Wave 1 internal service reference page. Covers the CMP (Privacy & Consent Management) service owned by Eric. Includes: service description, owner card, S/M/L tier breakdown, full agent check table (Quick Scan / Review / Full Audit), 5-level compliance framework, sample Quick Scan output, sample remediation plan, deliverables by tier, and current delivery workflow (Agent → Hayden/Lovable → Eric).

• –Eric — CMP / Privacy & Consent. Agent tool production-ready; public Quick Scan nearly complete.
• –Greg — CSP (Content Security Policy) & Uptime Monitoring.
• –Jenna — UX Design, Accessibility, UI, Wireframing, Prototyping.
• –Katelyn — Digital Strategy, UX Strategy, Content Design, Analytics, Competitive Benchmarking, Website Assessments.
• –Alex — SEO, Content Strategy, AI Search Optimization (GEO).
• –Ed — Digital Advertising (Google, Meta, LinkedIn, TikTok, Display, Remarketing).
• –Brian — HTTPS, Backup/DR (reactive only — not proactive service offerings).
• –Hayden — Report polish (Lovable). Produces branded client-facing reports from agent raw output.

• –S — Quick Scan: Free, self-serve on NWS website, homepage only, ~30 seconds, no account required.
• –M — Detailed Scan: ~$200, email-gated, deeper scan, agent-generated branded report.
• –L — Full Audit: $$$ TBD, full site, agent + specialist review, remediation plan.
• –XL — Consulting: $$$$ TBD, full audit + expert consultation, retainer entry point.

• – Created Paul, a project-level strategic planning agent defined at .claude/agents/paul.md. Paul reads project documentation, maps content against six planning dimensions (Product Definition, Stakeholders, Workstreams, Dependencies, Open Questions, Milestones), and asks structured questions to drive the planning process. Attributes (tone, question style, planning depth, priority focus, output format) are editable in the agent file.
• – Paul completed his first-round documentation review and identified four named open questions from the docs: Greg / uptime notifications, baseline assessment pricing ($TBD), x402 payment gateway decision, and prospect account creation. First round of planning questions posed — awaiting answers to produce phased workstream brief.

• –Who owns each of the four workstreams (Portal, Marketing Funnel, Sales Funnel, Uptime Monitor)? Build order vs. parallel?
• –Target launch state — deadline, specific pilot client, or still pre-pilot?
• –Baseline assessment pricing decision process — active or needs to be scoped here?
• –Free 10-page scan: lead-gen funnel into paid assessment, or standalone product?

• – All project assets renamed from NWS 365 / True North Advantage Plus (TNAP) to the canonical product name NWS-360. This is now the single name used across all files, documents, and deliverables for this product.

Before		After
Dashboard for NWS365.md	→	Dashboard for NWS-360.md
NWS365_Proposal_Meridian.docx	→	NWS-360_Proposal_Meridian.docx
nws365_team_branded.html	→	nws-360_team_branded.html
True North Advantage Plus.docx	→	NWS-360.docx