coilysiren/website

Watch

Refocus the hiring page around the agent-platform system #83

New issue

Closed

opened 2026-08-03 00:51:10 +00:00 by coilyco-ops · 1 comment

coilyco-ops commented

2026-08-03 00:51:10 +00:00

Collaborator

Parent

Private Inbox epic

Actor

Design role.

Outcome

Refresh the hiring page so a technical hiring leader can understand Kai's agent-platform thesis, strongest proof, and next action in one mobile screen.

Context

This is the second half of a time-boxed resume and hiring-page polish pass. The reusable positioning is: Kai builds the governed platform layer that lets engineering teams develop, ship, and operate agentic systems safely.

The page should show the system behind that claim, not repeat a job description. Ward is the strongest immediate proof. agent-compose and Ward MCP complete the larger platform story.

What to build

Lead with one plain sentence describing the platform outcome Kai owns.
Put the existing Ward infographic or an equally legible visual near the top when current repository evidence confirms it.
Present three proof routes: agent composition, governed execution, and guarded MCP delivery.
Make the resume, source repositories, and contact path obvious.
Keep the page specific enough to be credible and general enough to remain useful beyond one opportunity.
Use repository links until the dedicated project pages land. Each project-page child will upgrade its route.

Acceptance criteria

The first mobile screen communicates Kai's platform thesis and offers a clear next action.
Ward, agent-compose, and Ward MCP are presented as one coherent system rather than unrelated projects.
The page links to the refreshed resume and current public source evidence.
No prospective employer, recruiter interaction, private project, or unsupported claim appears.
Links work in an incognito session and layout remains legible on desktop and mobile.
Repository validation passes and the change lands through the repository's normal workflow.

Blocked by

None. Start immediately alongside the resume child.

Non-goals

Do not redesign the entire site.
Do not write three full project essays inside the hiring page.
Do not add generic enthusiasm, reach hashtags, or a company-specific pitch.
Do not hold the outbound email while waiting for later case-study pages.

## Parent [Private Inbox epic](https://forgejo.coilysiren.me/coilysiren/inbox/issues/319) ## Actor Design role. ## Outcome Refresh the hiring page so a technical hiring leader can understand Kai's agent-platform thesis, strongest proof, and next action in one mobile screen. ## Context This is the second half of a time-boxed resume and hiring-page polish pass. The reusable positioning is: Kai builds the governed platform layer that lets engineering teams develop, ship, and operate agentic systems safely. The page should show the system behind that claim, not repeat a job description. Ward is the strongest immediate proof. agent-compose and Ward MCP complete the larger platform story. ## What to build * Lead with one plain sentence describing the platform outcome Kai owns. * Put the existing Ward infographic or an equally legible visual near the top when current repository evidence confirms it. * Present three proof routes: agent composition, governed execution, and guarded MCP delivery. * Make the resume, source repositories, and contact path obvious. * Keep the page specific enough to be credible and general enough to remain useful beyond one opportunity. * Use repository links until the dedicated project pages land. Each project-page child will upgrade its route. ## Acceptance criteria * [ ] The first mobile screen communicates Kai's platform thesis and offers a clear next action. * [ ] Ward, agent-compose, and Ward MCP are presented as one coherent system rather than unrelated projects. * [ ] The page links to the refreshed resume and current public source evidence. * [ ] No prospective employer, recruiter interaction, private project, or unsupported claim appears. * [ ] Links work in an incognito session and layout remains legible on desktop and mobile. * [ ] Repository validation passes and the change lands through the repository's normal workflow. ## Blocked by None. Start immediately alongside the resume child. ## Non-goals * Do not redesign the entire site. * Do not write three full project essays inside the hiring page. * Do not add generic enthusiasm, reach hashtags, or a company-specific pitch. * Do not hold the outbound email while waiting for later case-study pages.

coilyco-ops referenced this issue

2026-08-03 00:51:51 +00:00

Publish an agent-compose case study for portable agent context #85

coilyco-ops referenced this issue

2026-08-03 00:51:51 +00:00

Publish a Ward MCP case study for guarded MCP delivery #86

coilyco-ops referenced this issue

2026-08-03 00:51:51 +00:00

Publish a Ward case study for governed agent execution #87

coilyco-ops added the

autonomy

headless

priority

labels

2026-08-03 00:53:15 +00:00

coilyco-ops commented

2026-08-03 02:05:17 +00:00

Author

Collaborator

Landed in ffc01ca433. The mobile entry view now leads with the governed agent-platform thesis, a clear resume/contact action, Ward as strongest proof, and linked agent-compose, Ward, and Ward MCP routes. The page remains employer-neutral, carries intentional noindex, nofollow metadata, and passed production mobile and desktop checks.

Landed in https://forgejo.coilysiren.me/coilysiren/website/commit/ffc01ca433ca54f4af1f574465a0ccd652b2d0fd. The mobile entry view now leads with the governed agent-platform thesis, a clear resume/contact action, Ward as strongest proof, and linked agent-compose, Ward, and Ward MCP routes. The page remains employer-neutral, carries intentional `noindex, nofollow` metadata, and passed production mobile and desktop checks.

coilyco-ops closed this issue

2026-08-03 02:05:18 +00:00

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

coilysiren/website#83

No description provided.

Rows
Columns