Build a public technical profile from a controlled claim register

Define the claim register

Use records for person, organisation, claim, source, project, capability and asset. A claim contains stable ID, statement, subject, type, status, owner, approved wording, source IDs, confidence, public/private classification, review date and expiry trigger.

Allowed states are proposed → verify → approved → retired. Corrections create a new version. Retirement removes the statement from generated pages while retaining the reason and prior evidence.

Resolve every material claim to a source

Prefer official records, Dylan-authored technical posts, controlled project artefacts and current system output. Search snippets supply leads only. Save source URL, publisher, publication date, retrieval UTC, exact locator and the claim it supports.

For a public forum post, store the full-name attribution, post URL and relevant technical signal. Quote only the minimum text required. A committee submission with multiple contributors supports collaboration evidence and cannot establish sentence-level authorship.

Generate the profile and ecosystem links

The canonical profile selects approved, current claims. Each capability links to at least one field note or controlled document. Each article returns to the relevant runbook, and each runbook returns to the article. The graph is useful when a reader can move from claim to method to external source in two or three clicks.

Use absolute canonical URLs. Run a link check over every internal route and resolve redirects or dead external evidence during the monthly review.

Publish conservative structured data

Use ProfilePage with a Person main entity on the canonical Dylan page. Publish only approved public attributes. Do not include private address, phone, inferred employer relationships or unverified sameAs profiles.

{
  "@context": "https://schema.org",
  "@type": "ProfilePage",
  "mainEntity": {"@type": "Person", "name": "Dylan Boekelman"}
}

Parse every JSON-LD block during the build and confirm that the canonical URL matches the deployed route.

Label composites, research and delivery evidence

A field note built from several real failure patterns is labelled composite. Independent tender research says that no client access or delivery occurred. A delivered project claim requires an artefact, approval and enough context to avoid exposing a client or restricted system.

These labels remove ambiguity without weakening the technical value. The method, commands and tests remain inspectable even when the scenario is synthetic.

Keep public and controlled evidence separate

The public graph stores URLs, redacted artefacts and approved statements. Credentials, tenant identifiers, production payloads, personal addresses and restricted logs remain in controlled storage. The claim record points to the internal evidence ID without copying it into the site.

Run metadata and secret scans on release packages. A generated site should contain the static output required for deployment and no working notes or source exports containing personal data.

Make publication a repeatable test

Validate one H1, language, viewport, canonical, meta description, JSON-LD, named links, heading order, keyboard focus, reduced motion and mobile table/code overflow. Crawl both sites and test every internal target. Check CSP, HSTS, referrer, permissions and content-type headers live.

Run the S8-VOICE-001 linter over article text. Decorative antithesis and abstract house terms are review candidates. Commands, identifiers and result branches should materially outnumber them.

Record the release and its limits

The release report lists changed claims, source checks, broken-link count, schema count, accessibility result, responsive result and immutable deployment IDs. A second reviewer opens the production routes and follows the reciprocal links.

A public evidence system improves traceability; it cannot verify a claim better than its source. Interview-derived evidence and current project artefacts should replace weak historical signals as they become available.