Fictional demonstration · not customer work

Northstar Workplace Studio: five-page agency delivery case

This purpose-built Next.js case shows the client report and developer ticket format offered to agencies: captured baseline, context decisions, prioritized remediation, and seven reviewed tickets. A final, separately labeled section tests the audit method in simulation; it is not part of the paid delivery.

Prepared forFictional Agency Partner

Client demonstrationNorthstar Workplace Studio

A real order may apply approved agency/client branding. The legal seller and actual reviewer cannot be concealed or misrepresented.

Pages reviewed: 5
Checks observed: 15 of 34
Baseline findings: 19
Developer tickets: 7

Inspect the machine-readable sampleBaseline results JSON Developer tickets JSON Developer tickets CSV Open questions JSON Handoff notes JSON

Executive readout

The baseline exposed a site-wide crawler block, an unavailable sitemap, incomplete page metadata, invalid structured data, thin raw HTML on several pages, and missing persistent trust/action paths. Nineteen deterministic findings and sixteen approved context decisions were consolidated into seven implementation tickets.

Reviewed scope

On a smaller screen, scroll the table horizontally.

One fictional public site; five named pages; shared discovery resources reviewed once.
Page	Demonstration URL
Home	https://northstar-workplace.example/
Services	https://northstar-workplace.example/services
Workplace review	https://northstar-workplace.example/workplace-review
About	https://northstar-workplace.example/about
Contact	https://northstar-workplace.example/contact

Priority remediation queue

The full queue contains 35 rows. The table below shows the P0 critical and P1 high-priority items that drive the seven grouped developer tickets.

On a smaller screen, scroll the table horizontally.

Critical and high-priority remediation rows.
ID	Priority	Affected page	Client-facing technical impact	Owner
RQ-001	P1	/	The raw response does not carry enough page content for a non-rendering client to identify the page purpose.	Agency developer with client copy approval
RQ-004	P0	/	The published global policy instructs standards-compliant crawlers not to retrieve any site path.	Client policy owner and agency developer
RQ-007	P1	/	The JSON-LD block cannot be parsed, so consumers cannot use that structured statement.	Agency developer with client factual approval
RQ-008	P1	/services	The raw response does not carry enough page content for a non-rendering client to identify the page purpose.	Agency developer with client copy approval
RQ-009	P1	/services	The response omits a page title, weakening deterministic identification in browser and machine-readable metadata.	Agency developer with client copy approval
RQ-011	P1	/workplace-review	The raw response does not carry enough page content for a non-rendering client to identify the page purpose.	Agency developer with client copy approval
RQ-014	P1	/about	The raw response does not carry enough page content for a non-rendering client to identify the page purpose.	Agency developer with client copy approval
RQ-016	P1	/contact	The raw response does not carry enough page content for a non-rendering client to identify the page purpose.	Agency developer with client copy approval
RQ-017	P1	/contact	The response omits a page title, weakening deterministic identification in browser and machine-readable metadata.	Agency developer with client copy approval
RQ-020	P1	/	The visible provider identity has no matching machine-readable provider statement on its canonical source page.	Client factual approver and agency developer
RQ-023	P1	/	The scoped page does not expose the client-approved public contact path.	Client operations owner and agency developer
RQ-024	P1	/services	The visible service has no matching machine-readable service statement on its canonical source page.	Client factual approver and agency developer
RQ-027	P1	/workplace-review	The visible service has no matching machine-readable service statement on its canonical source page.	Client factual approver and agency developer
RQ-030	P1	/workplace-review	The scoped page does not expose the client-approved public contact path.	Client operations owner and agency developer
RQ-035	P1	/contact	The scoped page does not expose the client-approved public contact path.	Client operations owner and agency developer

Developer ticket pack

Each ticket groups related findings into one assignable change. The evidence boundary prevents the technical recommendation from becoming an unsupported outcome claim.

CHG-001

Replace the global crawler block with the client-approved policy

P0S effort

Owner: Client policy owner and agency developer

Affected pages

Suggested file targets

app/robots.ts. These are location suggestions for the identified framework, not delivered code.

Observed evidence

RQ-003: robots.txt does not declare a sitemap
RQ-004: robots.txt appears to block the entire site

Potential technical impact

RQ-003: The crawler-policy resource does not point standards-compliant clients to the sitemap.
RQ-004: The published global policy instructs standards-compliant crawlers not to retrieve any site path.

Recommended change

RQ-003: Add an absolute Sitemap directive.
RQ-004: Confirm this is intentional; otherwise narrow the disallow rules.

Dependencies

Client policy owner approves the crawler policy

Acceptance criteria

GET /robots.txt returns a valid text resource.
The approved policy does not contain a global Disallow: / rule.
The resource declares the canonical sitemap URL.

Evidence references

RQ-003 · DISCOVERY-03//::DISCOVERY-03
RQ-004 · DISCOVERY-04//::DISCOVERY-04

Client must approve crawler policy; no ranking or traffic effect is predicted.

CHG-002

Publish the five scoped canonical URLs in a valid XML sitemap

P2S effort

Owner: Agency developer

Affected pages

Suggested file targets

app/sitemap.ts. These are location suggestions for the identified framework, not delivered code.

Observed evidence

RQ-002: sitemap.xml was unavailable

Potential technical impact

RQ-002: The site does not expose a valid XML inventory at the standard sitemap path.

Recommended change

RQ-002: Publish a canonical sitemap and reference it from robots.txt.

Dependencies

Canonical origin and five-page scope are final

Acceptance criteria

GET /sitemap.xml returns a valid XML urlset.
The urlset contains exactly the five reviewed scope URLs.
Every listed URL uses the canonical origin.

Evidence references

RQ-002 · DISCOVERY-02//::DISCOVERY-02

This creates a deterministic discovery resource; no indexing outcome is claimed.

CHG-003

Add reviewed metadata and useful raw page copy

P1M effort

Owner: Agency developer with client copy approval

Affected pages

/, /services, /about, /contact

Suggested file targets

app/layout.tsx, app/page.tsx, app/services/page.tsx, app/workplace-review/page.tsx, app/about/page.tsx, app/contact/page.tsx. These are location suggestions for the identified framework, not delivered code.

Observed evidence

RQ-001: Raw HTML contains little readable page content
RQ-005: No substantive meta description was detected
RQ-008: Raw HTML contains little readable page content
RQ-009: No useful HTML title was detected
RQ-014: Raw HTML contains little readable page content
RQ-015: No substantive meta description was detected
RQ-016: Raw HTML contains little readable page content
RQ-017: No useful HTML title was detected
RQ-018: No substantive meta description was detected

Potential technical impact

RQ-001: The raw response does not carry enough page content for a non-rendering client to identify the page purpose.
RQ-005: The response omits a substantive summary of the page purpose.
RQ-008: The raw response does not carry enough page content for a non-rendering client to identify the page purpose.
RQ-009: The response omits a page title, weakening deterministic identification in browser and machine-readable metadata.
RQ-014: The raw response does not carry enough page content for a non-rendering client to identify the page purpose.
RQ-015: The response omits a substantive summary of the page purpose.
RQ-016: The raw response does not carry enough page content for a non-rendering client to identify the page purpose.
RQ-017: The response omits a page title, weakening deterministic identification in browser and machine-readable metadata.
RQ-018: The response omits a substantive summary of the page purpose.

Recommended change

RQ-001: Server-render the core identity, offer, evidence, and navigation content.
RQ-005: Add a plain-language description of the entity, audience, and offer.
RQ-008: Server-render the core identity, offer, evidence, and navigation content.
RQ-009: Add a specific title naming the entity and primary offer.
RQ-014: Server-render the core identity, offer, evidence, and navigation content.
RQ-015: Add a plain-language description of the entity, audience, and offer.
RQ-016: Server-render the core identity, offer, evidence, and navigation content.
RQ-017: Add a specific title naming the entity and primary offer.
RQ-018: Add a plain-language description of the entity, audience, and offer.

Dependencies

Client fact reviewer approves all business, identity, and service copy

Acceptance criteria

Every scoped response contains a useful title.
Every scoped response contains a description of at least 20 characters.
The home, services, about, and contact responses contain enough reviewed raw HTML text to identify their page purpose.
Client approves every identity and service statement.

Evidence references

RQ-001 · ACCESS-02//::ACCESS-02
RQ-005 · IDENTITY-02//::IDENTITY-02
RQ-008 · ACCESS-02/services/services::ACCESS-02
RQ-009 · IDENTITY-01/services/services::IDENTITY-01
RQ-014 · ACCESS-02/about/about::ACCESS-02
RQ-015 · IDENTITY-02/about/about::IDENTITY-02
RQ-016 · ACCESS-02/contact/contact::ACCESS-02
RQ-017 · IDENTITY-01/contact/contact::IDENTITY-01
RQ-018 · IDENTITY-02/contact/contact::IDENTITY-02

Metadata reflects only reviewed fixture copy; click-through or ranking effects are not claimed.

CHG-004

Declare a self-referencing canonical URL on every scoped page

P2S effort

Owner: Agency developer

Affected pages

/, /services, /workplace-review, /contact

Suggested file targets

app/page.tsx, app/services/page.tsx, app/workplace-review/page.tsx, app/about/page.tsx, app/contact/page.tsx. These are location suggestions for the identified framework, not delivered code.

Observed evidence

RQ-006: No valid same-page canonical URL was detected
RQ-010: No valid same-page canonical URL was detected
RQ-013: No valid same-page canonical URL was detected
RQ-019: No valid same-page canonical URL was detected

Potential technical impact

RQ-006: The page does not declare its own reviewed preferred URL.
RQ-010: The page does not declare its own reviewed preferred URL.
RQ-013: The page does not declare its own reviewed preferred URL.
RQ-019: The page does not declare its own reviewed preferred URL.

Recommended change

RQ-006: Add a canonical link that resolves to this page on the same public origin.
RQ-010: Add a canonical link that resolves to this page on the same public origin.
RQ-013: Add a canonical link that resolves to this page on the same public origin.
RQ-019: Add a canonical link that resolves to this page on the same public origin.

Dependencies

Canonical origin and scoped pathnames are final

Acceptance criteria

Each canonical resolves to the same origin and same normalized pathname as its response URL.
No scoped page points to a different service page.

Evidence references

RQ-006 · IDENTITY-03//::IDENTITY-03
RQ-010 · IDENTITY-03/services/services::IDENTITY-03
RQ-013 · IDENTITY-03/workplace-review/workplace-review::IDENTITY-03
RQ-019 · IDENTITY-03/contact/contact::IDENTITY-03

The check validates declared preferred URLs, not search-engine selection.

CHG-005

Server-render the workplace-review service explanation

P1M effort

Owner: Agency developer with client copy approval

Affected pages

/workplace-review

Suggested file targets

app/workplace-review/page.tsx. These are location suggestions for the identified framework, not delivered code.

Observed evidence

RQ-011: Raw HTML contains little readable page content
RQ-012: No substantive meta description was detected

Potential technical impact

RQ-011: The raw response does not carry enough page content for a non-rendering client to identify the page purpose.
RQ-012: The response omits a substantive summary of the page purpose.

Recommended change

RQ-011: Server-render the core identity, offer, evidence, and navigation content.
RQ-012: Add a plain-language description of the entity, audience, and offer.

Dependencies

Client fact reviewer approves the service purpose, process, limitations, and action copy

Acceptance criteria

The raw workplace-review HTML contains the service purpose, process, limitations, and valid next action.
The audited visible-text count is at least 800 characters.

Evidence references

RQ-011 · ACCESS-02/workplace-review/workplace-review::ACCESS-02
RQ-012 · IDENTITY-02/workplace-review/workplace-review::IDENTITY-02

This proves raw retrieval of reviewed copy, not reader understanding or conversion.

CHG-006

Repair invalid JSON-LD and add reviewed provider/service nodes

P1M effort

Owner: Agency developer with client factual approval

Affected pages

/, /services, /workplace-review

Suggested file targets

app/page.tsx, app/services/page.tsx, app/workplace-review/page.tsx. These are location suggestions for the identified framework, not delivered code.

Observed evidence

RQ-007: At least one JSON-LD block could not be parsed
RQ-020: No named, visibly matching organization structured data was detected
RQ-024: No Product, Service, Offer, or SoftwareApplication schema was detected
RQ-027: No Product, Service, Offer, or SoftwareApplication schema was detected

Potential technical impact

RQ-007: The JSON-LD block cannot be parsed, so consumers cannot use that structured statement.
RQ-020: The visible provider identity has no matching machine-readable provider statement on its canonical source page.
RQ-024: The visible service has no matching machine-readable service statement on its canonical source page.
RQ-027: The visible service has no matching machine-readable service statement on its canonical source page.

Recommended change

RQ-007: Repair invalid JSON and validate every structured-data block.
RQ-020: If applicable, add accurate named Organization, LocalBusiness, ProfessionalService, or Corporation JSON-LD that matches visible identity text.
RQ-024: If applicable, describe only real, public offers with matching visible-page details.
RQ-027: If applicable, describe only real, public offers with matching visible-page details.

Dependencies

CHG-003 visible identity and service copy is approved
Client fact reviewer approves provider and service facts

Acceptance criteria

Every application/ld+json block parses as JSON.
Organization identity matches visible page copy.
Service nodes describe only the two visible public services.

Evidence references

RQ-007 · STRUCTURE-03//::STRUCTURE-03
RQ-020 · STRUCTURE-01//::STRUCTURE-01
RQ-024 · STRUCTURE-02/services/services::STRUCTURE-02
RQ-027 · STRUCTURE-02/workplace-review/workplace-review::STRUCTURE-02

Structured statements are fixture facts, not third-party validation or eligibility guarantees.

CHG-007

Publish persistent policy links and one reviewed contact action

P1M effort

Owner: Client operations owner and agency developer

Affected pages

/, /services, /workplace-review, /about, /contact

Suggested file targets

components/SiteShell.tsx, app/contact/page.tsx. These are location suggestions for the identified framework, not delivered code.

Observed evidence

RQ-021: No privacy link was detected on the homepage
RQ-022: No terms or legal link was detected on the homepage
RQ-023: No clear action with a valid destination was detected
RQ-025: No privacy link was detected on the homepage
RQ-026: No terms or legal link was detected on the homepage
RQ-028: No privacy link was detected on the homepage
RQ-029: No terms or legal link was detected on the homepage
RQ-030: No clear action with a valid destination was detected
RQ-031: No privacy link was detected on the homepage
RQ-032: No terms or legal link was detected on the homepage
RQ-033: No privacy link was detected on the homepage
RQ-034: No terms or legal link was detected on the homepage
RQ-035: No clear action with a valid destination was detected

Potential technical impact

RQ-021: The scoped page does not expose the client-approved privacy path in persistent navigation.
RQ-022: The scoped page does not expose the client-approved terms path in persistent navigation.
RQ-023: The scoped page does not expose the client-approved public contact path.
RQ-025: The scoped page does not expose the client-approved privacy path in persistent navigation.
RQ-026: The scoped page does not expose the client-approved terms path in persistent navigation.
RQ-028: The scoped page does not expose the client-approved privacy path in persistent navigation.
RQ-029: The scoped page does not expose the client-approved terms path in persistent navigation.
RQ-030: The scoped page does not expose the client-approved public contact path.
RQ-031: The scoped page does not expose the client-approved privacy path in persistent navigation.
RQ-032: The scoped page does not expose the client-approved terms path in persistent navigation.
RQ-033: The scoped page does not expose the client-approved privacy path in persistent navigation.
RQ-034: The scoped page does not expose the client-approved terms path in persistent navigation.
RQ-035: The scoped page does not expose the client-approved public contact path.

Recommended change

RQ-021: If required by those practices, publish a reviewed privacy notice and link it from persistent navigation.
RQ-022: If applicable, publish reviewed terms appropriate to those activities.
RQ-023: If applicable, the agency or client approves one stable public action, then a ReadableOps human verifies the destination before delivery.
RQ-025: If required by those practices, publish a reviewed privacy notice and link it from persistent navigation.
RQ-026: If applicable, publish reviewed terms appropriate to those activities.
RQ-028: If required by those practices, publish a reviewed privacy notice and link it from persistent navigation.
RQ-029: If applicable, publish reviewed terms appropriate to those activities.
RQ-030: If applicable, the agency or client approves one stable public action, then a ReadableOps human verifies the destination before delivery.
RQ-031: If required by those practices, publish a reviewed privacy notice and link it from persistent navigation.
RQ-032: If applicable, publish reviewed terms appropriate to those activities.
RQ-033: If required by those practices, publish a reviewed privacy notice and link it from persistent navigation.
RQ-034: If applicable, publish reviewed terms appropriate to those activities.
RQ-035: If applicable, the agency or client approves one stable public action, then a ReadableOps human verifies the destination before delivery.

Dependencies

Client operations owner approves privacy, terms, and contact destinations
A human verifies contact destination ownership and delivery before production

Acceptance criteria

Every scoped page links to privacy and terms routes.
The contact page exposes one valid reviewed mailto destination.
A human verifies destination ownership and delivery before production.

Evidence references

RQ-021 · TRUST-01//::TRUST-01
RQ-022 · TRUST-02//::TRUST-02
RQ-023 · ACTION-01//::ACTION-01
RQ-025 · TRUST-01/services/services::TRUST-01
RQ-026 · TRUST-02/services/services::TRUST-02
RQ-028 · TRUST-01/workplace-review/workplace-review::TRUST-01
RQ-029 · TRUST-02/workplace-review/workplace-review::TRUST-02
RQ-030 · ACTION-01/workplace-review/workplace-review::ACTION-01
RQ-031 · TRUST-01/about/about::TRUST-01
RQ-032 · TRUST-02/about/about::TRUST-02
RQ-033 · TRUST-01/contact/contact::TRUST-01
RQ-034 · TRUST-02/contact/contact::TRUST-02
RQ-035 · ACTION-01/contact/contact::ACTION-01

The automated audit validates syntax and public-network safety only; it does not send a message or prove response behavior.

Open client-fact questions

Public evidence cannot establish client intent, approval, ownership, or undisclosed business facts. The delivery assigns each open question to a named client role instead of drafting an answer as truth.

OQ-001

What crawler policy does the client approve for the public site?

Accountable owner: Client policy owner

Related tickets: CHG-001

The public response shows the current policy, but public evidence cannot establish the client's intended future policy.

OQ-002

Which provider, service, and identity statements does the client approve as current facts?

Accountable owner: Client fact reviewer

Related tickets: CHG-003, CHG-005, CHG-006

ReadableOps can compare structured statements with visible copy but cannot independently establish undisclosed business facts.

OQ-003

Which privacy, terms, and contact destinations are approved, owned, and monitored?

Accountable owner: Client operations owner

Related tickets: CHG-007

Public syntax and links can be inspected, but ownership, approval, and response behavior require a human confirmation.

Agency handoff notes

The handoff pack carries the priority order, open questions, responsibilities, and correction status into the agency review.

P0/P1 first-pass priority order

CHG-001 · P0 — Replace the global crawler block with the client-approved policy
CHG-003 · P1 — Add reviewed metadata and useful raw page copy
CHG-005 · P1 — Server-render the workplace-review service explanation
CHG-006 · P1 — Repair invalid JSON-LD and add reviewed provider/service nodes
CHG-007 · P1 — Publish persistent policy links and one reviewed contact action

Responsibilities

ReadableOps records the scoped public evidence and prepares the reviewed delivery.
The agency or client confirms business facts and approves every recommendation.
The agency or client tests and deploys every production change.

Correction status: No factual correction recorded in this demonstration

Controlled simulation — not a customer outcome

The same engine and checkset inspected the same five-page scope after the seven ticket groups were applied to a controlled fixture. This demonstrates comparison behavior; it is not a customer re-audit, production deployment, or deliverable in the $350 offer.

Baseline: 15/34 checks observed
Simulated retest: 34/34 checks observed
Resolved findings: 19
Introduced / persistent: 0 / 0

This comparison proves only deterministic technical changes in the controlled fixture. It does not prove a live deployment, ranking, citation, traffic, conversion, time saving, cost saving, or revenue effect.

Evidence provenance

Engine: readableops-site-audit 0.4.0
Checkset: 2026-07-24.4
Baseline scope SHA-256: 1810658614967fd21a4413293d9bd3c847c0917efe6e7df74e2d558ea036cd2a
Retest scope SHA-256: eeaae53e1f8bcd3fd58ee81a3dc435c6ad8e7e3e5bbe0999fc28c0a21c5eb2b8

What this demonstration does not establish

Northstar Workplace Studio and Fictional Agency Partner are fictional. This is not a customer engagement, testimonial, paid pilot, live deployment, proof of demand, or evidence that ReadableOps saves time or improves commercial outcomes.

Download the PDF Return to the offer