01Technical Evidence

02By occasion

Which audit focus interests you?

01 · Prove the machine room

010203040510

02 · Institutionalize trust

06080912

03 · Operationalize AI visibly

0711

03The reading

Every tile, in full.

Performance / Core Web Vitals baseline logic

Performance

Public performance is treated as a recurring quality signal using lightweight pages, static delivery, compressed assets and periodic browser checks.

Check it yourself

Run PageSpeed Insights on any route: the pages are static and light by design.

Lighthouse / PSI baseline process

Performance

Lighthouse and PageSpeed-style checks are used as directional evidence during major implementation waves, with issues documented rather than hidden.

Check it yourself

Directional evidence, checkable in the open; issues are documented, not hidden.

Hosting / CDN / Cloudflare note

Delivery

The public site is packaged as static files and deployed through Cloudflare Pages/CDN logic for global delivery.

Check it yourself

Static files behind Cloudflare Pages/CDN, visible in response headers.

Security header baseline

Security

Conservative headers are present in _headers, including nosniff, referrer policy, permissions policy, HSTS and report-only CSP logic.

Check it yourself

Inspect the response headers: nosniff · referrer-policy · permissions-policy · HSTS · report-only CSP.

Sitemap / robots / indexing hygiene

Indexing

Public routes are listed in sitemap.xml, with private client assets excluded and robots referencing the canonical sitemap.

Check it yourself

Open /sitemap.xml and /robots.txt: public routes in, private client assets out.

Structured data status

Indexing

Core pages use conservative JSON-LD such as WebPage, Organization, Service and BreadcrumbList where appropriate. No review or rating schema is invented.

Check it yourself

View page source: JSON-LD blocks (WebPage, Organization, Service, BreadcrumbList). No invented ratings.

No-storage diagnostic tools

Diagnostics

The Execution Signal Assessment™ runs in the browser and does not submit answers, store responses or create a backend record.

Check it yourself

Run the assessment with the network tab open: no submission, no backend record.

Scope of the file

Security

Formal certifications (penetration test, SOC 2, ISO, certified accessibility statement, legal compliance certification) sit outside the scope of this file; where a mandate needs one, it is scoped openly at the start.

Consent-gated optional analytics

Data

Matomo is not active: no Matomo script is loaded and no Matomo event is queued. The current public HTML contains no Matomo URL or site ID.

Check it yourself

Search the public HTML: no Matomo URL, no site ID, no analytics script.

Range-capable media delivery

Delivery

Full-length homepage films are served from media.kulicadvisory.com on Cloudflare R2. The public media endpoint supports byte-range delivery for native seeking.

Check it yourself

Seek inside a homepage film: byte-range responses from media.kulicadvisory.com.

AICTIONBOT™ Signal Guide API

Diagnostics

The Signal Guide’s optional AI signal read posts to a same-origin /api/signal-guide endpoint handled by a Cloudflare Pages Worker. Requests are POST-only JSON with a 1,200-character limit and a six-turn context cap; responses are no-store. The Anthropic API key stays server-side, prompts are not logged raw, no transcript is stored by the website, and a deterministic offline fallback answers when the provider is unavailable or the feature is disabled.

The tools of the AICTIONBOT™ Workbench use the same endpoint in a mode of their own for document text and images; nothing is stored there either. In addition there is the MCP endpoint /mcp (Streamable HTTP without a session, POST JSON-RPC) for Claude, ChatGPT and other programs: the lookups work without sign-in and are rate-limited; the checks and the AI tools after sign-in through OAuth 2.1 with PKCE, with a licence or, without one, one check per connection every 30 days. The licence key sits encrypted in the token and not on the server.

Check it yourself

POST-only /api/signal-guide · 1,200-char limit · six-turn cap · responses no-store.

Durable Executive Intake

Data

Executive Intake submits to the same-origin /api/executive-intake endpoint handled by the Pages Worker. The request is validated before accepted fields are stored first in Cloudflare D1; the browser receives a short KA reference. The Worker uses a field allowlist, honeypot, isolated rate limit, idempotent submission ID and attachment rejection. Email is a secondary notification through a private mailer Worker and cannot decide whether the D1 record exists. Preview and Production use separate databases; records expire after 30 calendar days and scheduled cleanup removes expired rows. Intake fields are not sent to Matomo or written to Analytics Engine, and the Intake record does not store IP address, user agent, cookies or analytics identifiers.

Check it yourself

/api/executive-intake · field allowlist · 30-day expiry · no IP, UA, cookies or analytics IDs stored.

04Good to know

Claim honesty

Scope of the file · tile 08

Where this file ends and a formal mandate begins.

This page makes the public technical evidence layer visible while formal certification, compliance and security audits remain separate, clearly scoped mandates.

Where a mandate needs one of these, it is said openly: documented rather than hidden.

Said before you ask

Scope, stated plainly: this file documents public technical hygiene and evidence logic; formal certifications are separate, clearly scoped mandates. It documents the public technical hygiene and evidence logic used to make the website more transparent for enterprise buyers.

24h implementation response

Prove the machine room. Institutionalize trust. Operationalize AI visibly.