Edward A. Neyhart

Step 7 of 7 · How it's built

This site, showing its own making

Cucumbs builds Cucumbs. This page shows how the profile was put together: the loop it went through, the rules it follows, and the checks it passed.

Root: axiom II Form follows function; function follows flow. The pairing is this site's own reading.

The build, as a packet

work.cucumbs.com, version 3

SOURCE → TARGET
Core → Athena, for review
TASK
Make the seven pages read as one journey, and make the site feel like one room in the Cucumbs house.
STATE
Version 2 added the seven pages and four interactive parts. Version 3 joins them into one reading path, with a handoff at the end of each page, the shared Cucumbs network bar, and more depth in the design.
OBSERVATIONS
  • FACTThe hub at cucumbs.com sets the shared look: dark background, vine green, and a cream accent for Edward.
EVIDENCE
  • FACTEvery career line traces to Edward's career record.
  • FACTThe axioms match Edward's canonical text word for word.
HYPOTHESES
  • INFERREDShowing the evidence tag on each claim makes the profile easier to trust.
UNCERTAINTIES
  • UNKNOWNWhether Athena wants changes. Her review decides.
REQUEST
Review, then publish or send back notes.
RETURN
Notes go into the next round of this loop.

The loop that made it

  1. Observe

    Read the public hub at cucumbs.com and the feedback on version 1.

  2. Understand

    Read Edward's career record in full and marked which lines are ready for public use.

  3. Decompose

    Split the site into an overview, the record, the loop, worked examples, a role-fit tool, the Cucumbs context and this page.

  4. Delegate

    Kept the facts to Edward's career record, with only tools and skills on his record. Took the look from the shared Cucumbs tokens and the hub, and the axioms from Edward's canonical text.

  5. Compare

    Checked each page against the hub's look and structure, and each claim against the record.

  6. Synthesize

    Wrote the pages in plain language, with evidence tags on the claims.

  7. Act

    Built static pages, one stylesheet and one script file. No outside requests and no storage.

  8. Recurse

    Ran the checks, fixed what they found, and handed the result to Athena for review. Her notes start the next round.

Rules it follows

  • Every claim about Edward comes from his career record.
  • The education line reads exactly: University of Georgia, Philosophy | Some college.
  • Only tools and skills on his record.
  • AI work is described only as proprietary, since 2022. No methods.
  • LinkedIn is the only contact. No phone, email, address or form.
  • Nothing private from Cucumbs: no methods and no private details.
  • No inline scripts or styles, no outside requests, no cookies or browser storage.
  • Every page works with JavaScript off.
  • Plain writing, checked with an offline plain-writing pass.

Files

index.htmlHome: the thread
overview/Overview
record/Career record
practice/How he works
examples/Worked examples and drill
fit/Role-fit tool
cucumbs/Cucumbs context and axioms
built/This page
assets/tokens.cssShared Cucumbs tokens, copied unchanged
assets/site.cssThis site's styles
assets/network-bar.cssThe shared Cucumbs network bar, copied unchanged from the hub
assets/site.jsThe four interactive parts
assets/thread.css, assets/thread.jsThe thread on the home page
_headersSecurity headers
404.html, robots.txt, favicon.svgSupporting files

Checks it passed

Banned-term scanSearches every file for words the site must never use.
Contact scanLooks for phone numbers and email addresses.
Inline-code scanLooks for inline scripts, inline styles and inline event handlers.
Outside-link checkLists every outside address. Only LinkedIn and the Cucumbs sites are allowed.
HTML parseConfirms every page's tags open and close properly.
Local serveServes the site locally with the real security headers so the content policy is enforced.
ScreenshotsDesktop and mobile, with JavaScript on and off, plus a check for browser errors.
Claims checkCompares every sentence about Edward with the last reviewed version, so a design pass can't change a fact.
ReviewAthena reviews before anything goes live. Edward has the final say.

Back to the Cucumbs hub

How this page was built

Sections

  • The build, as a packet
  • The loop that made it
  • Rules it follows
  • Files
  • Checks it passed

Sources

  • This site's own files and checks

Interactive part

None. This page is plain HTML and CSS.

It runs in your browser, sends nothing and stores nothing. With JavaScript off, the page still shows everything.

Checks before review

Banned-term scan, inline-code scan, outside-link check, HTML parse, a local serve, and screenshots on desktop and mobile with JavaScript on and off.

The full build record