diff --git a/LAUNCH.md b/LAUNCH.md index e6a8a90..668ace7 100644 --- a/LAUNCH.md +++ b/LAUNCH.md @@ -2,12 +2,14 @@ Your job search should remember what you've done. -Relay is an early SyberLabs product for people using AI to research jobs and prepare applications. It brings repeated postings, source history, missing facts and exact drafts into one review workspace. +Relay is SyberLabs' job-search product: a private review workspace that remembers the roles you researched, the drafts you accepted, and the interviews you started. Assistants help you write; Relay keeps the record. -Import research from Notion, exchange packets with Grok Bot, or prepare a draft with Claude. Review the actual words before using them. Keep interview notes without resetting your application status. +Import research from Notion or a tracker CSV, exchange packets with ChatGPT, Codex, Grok Bot, or Claude, and review the actual words before using them. Keep interview notes without resetting your application status. Available now: the application workspace and local command integrations. Account connections require setup. Autonomous hunting and application sending are not included in this release. Explore the code and setup guide: https://github.com/SyberLabs/relay -No customer counts, hiring outcomes or throughput improvements have been claimed. This copy is suitable for the repository launch; no social post has been sent. +Lead engineer: Seth Carlson. Application development: Mateo. + +No customer counts, hiring outcomes, or throughput improvements have been claimed. This copy is suitable for the repository; no social post has been sent. diff --git a/README.md b/README.md index 0281beb..f4e7ed3 100644 --- a/README.md +++ b/README.md @@ -3,76 +3,86 @@ **Your job search should remember what you've done.** -A job-search review workspace that keeps research, application history, and exact accepted drafts together across your tools. +SyberLabs' job-search product: a private review workspace that remembers the roles you researched, the drafts you accepted, and the interviews you started. Assistants help you write; Relay keeps the record. -**Lead engineer: [Seth Carlson](https://github.com/sdcarlson).** +**Lead engineer: [Seth Carlson](https://github.com/sdcarlson).** Application development: [Mateo](https://github.com/sykosyber). ## Available in this early release -- Consolidate repeated posting URLs while preserving source history. -- Keep interview notes and follow-ups without resetting application status. -- Accept an exact draft; changing the wording requires review again. -- Import a tracker CSV through explicit column mapping and a record preview. Source statuses remain research; existing Relay status and accepted drafts are preserved. +- One history per job: matching posting URLs join the same record, and earlier research stays visible. +- Exact draft acceptance: you approve specific wording; changing it requires review again. +- Interview notes and follow-ups that do not reset a submitted or live-loop application. +- Import a tracker CSV through column mapping and a record preview. Imported statuses stay research; existing Relay status and accepted drafts are preserved. - Explore fictional example records; no real applicant data is included. ## Integrations -- **[ChatGPT](integrations/OPENAI.md)**: Prepared prompts and JSON file handoffs for draft review. -- **[Codex](integrations/OPENAI.md)**: Prepared prompts, validated draft files, or local drafting through the signed-in Codex CLI. -- **[Obsidian](integrations/OBSIDIAN.md)**: Selected research notes, version-bound draft notes, and job context exports. -- **[Notion](integrations/README.md)**: Read-only research import through the local command connector. -- **[Claude](integrations/README.md)**: Draft preparation through the Claude API with your own credentials. -- **[Grok Bot](integrations/GROK_BOT.md)**: Validated research and draft file exchange in the Bot's VM. -- **[Tracker CSV](integrations/README.md)**: Explicit column mapping and preview of a local comma-separated tracker file as research. +- **[ChatGPT](integrations/OPENAI.md)**: Prepare a job packet and prompt, then bring a JSON draft back for review. +- **[Codex](integrations/OPENAI.md)**: The same packet, plus optional local drafting through the signed-in Codex CLI. +- **[Obsidian](integrations/OBSIDIAN.md)**: Selected research notes, version-bound draft edits, and job-context exports from your vault. +- **[Notion](integrations/README.md)**: Read-only research import through a local command you run with your own credentials. +- **[Claude](integrations/README.md)**: Draft preparation from your verified facts through the Claude API, using your own key. +- **[Grok Bot](integrations/GROK_BOT.md)**: Validated research and draft file exchange inside the Bot's VM. +- **[Tracker CSV](integrations/README.md)**: Map columns, preview rows, and import a local tracker file as research. -Integrations require explicit setup or file handoffs. Returned drafts require human review. No automatic application sending or background account sync is included. +You stay in control. Integrations are explicit file and command handoffs. Every returned draft needs human review. Relay does not send applications or sync accounts in the background. -ChatGPT uses a prompt/file handoff; Codex also supports a local CLI adapter. This release does not include a hosted ChatGPT app or MCP connection. +ChatGPT uses a prompt and file handoff; Codex also supports a local CLI adapter. This release does not include a hosted ChatGPT app or MCP connection. [Integration setup](integrations/README.md) | [ChatGPT and Codex guide](integrations/OPENAI.md) | [Launch copy](LAUNCH.md) -Tracker CSV imports are also available through explicit column mapping and preview. Source statuses remain research; existing Relay status and accepted drafts are preserved. [Tracker CSV setup](integrations/README.md#tracker-csv--relay). - -[Development workflow](CONTRIBUTING.md) | [Delivery and review](docs/delivery.md) | [Team board](https://github.com/orgs/SyberLabs/projects/1) - ## Why Relay -When another assistant rediscovers a role or rewrites a draft, you need to know what came before and whether the new text was actually reviewed. Relay makes those distinctions explicit: +People already use ChatGPT, Claude, Grok, Notion, and Obsidian to hunt for jobs. The work still falls apart in the gaps: a new chat forgets the last draft, a tracker overwrites a decision, an interview note resets application status. + +Relay is the workspace that remembers. Import research as evidence. Review the actual words. Accept a specific draft. Keep follow-ups on submitted jobs without losing what you already did. - **Research keeps its history.** Matching posting URLs join the existing opportunity; changed source notes remain separate observations. Rediscovery preserves an existing interview or submitted status. - **Acceptance belongs to the text.** An imported Ready label does not approve a new draft. Accept it in Relay; changing the accepted text requires another review. - **Handoffs belong to a job and version.** Draft packets and editor checks reject stale work instead of silently replacing a newer review. -- **Bring the tools you already use.** Selected notes and validated files can supply research and drafts. Relay keeps the review record across those handoffs. +- **Bring the tools you already use.** ChatGPT, Codex, Claude, Grok Bot, Notion, Obsidian, and a tracker CSV can supply research and drafts. Relay keeps the review record across those handoffs. + +Relay records acceptance inside its workspace. It does not send applications, verify every claim, or prove which words were submitted to an employer. URL matching cannot identify every repost across different job boards. + +## Team + +Relay is built at [SyberLabs](https://github.com/SyberLabs) by a two-person team: + +- **[Seth Carlson](https://github.com/sdcarlson)** - lead engineer and product +- **[Mateo](https://github.com/sykosyber)** - application development and review -For example: import a role from Notion, prepare a draft with Claude, accept it, and later add an Obsidian research note for the same posting. The note adds context without replacing your draft or approving new wording. A later draft change needs review again. +Every database read and write belongs to the authenticated user. Exact accepted text is versioned. Imports add evidence; they cannot grant approval. A stale editor or assistant packet cannot overwrite newer work. -This is Relay's product focus, not a claim of exclusive features or a proven advantage. Job tracking, AI writing, interview notes, and human review already exist elsewhere. Relay records acceptance inside its workspace; it does not verify every claim or prove which words were submitted to an employer. URL matching also cannot identify every repost across different job boards. +[Development workflow](CONTRIBUTING.md) · [Delivery and review](docs/delivery.md) · [Team board](https://github.com/orgs/SyberLabs/projects/1) +## Stack -## GrokCell bot templates +React 19 and Vinext on Cloudflare Workers, with D1 persistence and Drizzle migrations. TypeScript throughout. Local development uses Sites authentication; production uses a verified Cloudflare Access gateway and separate staging and production databases. -For model-specific research practices, reusable handoffs, and a proposed evaluation plan, see [Context management for Relay](context-management/README.md). The guide distinguishes documented provider capabilities from Relay's implemented integrations. +See [architecture and data ownership](ARCHITECTURE.md) and [hosting and recovery](docs/hosting.md). -The [GrokCell folder](grokcell/README.md) includes First Principles, Product Ideation, Red Flag, and Garbage Collector with their source instructions, profiles, public bot links, and behavior checks. Use a specialist when its purpose fits the task. These templates do not connect to Relay or grant access to application records automatically; the [Relay adapter](integrations/GROK_BOT.md) remains the guide for exchanging job research and drafts. +## Using Relay with the tools you already have -This is a pinned copy of the separately maintained, MIT-licensed [GrokCell project](https://github.com/sdcarlson/grokcell). Propose template improvements upstream, then refresh the copy following [its source record](grokcell/UPSTREAM.md). +Use your preferred discovery and application tools alongside Relay. [Simplify](https://simplify.jobs/) already offers job matching, autofill, resume tailoring, and tracking. Relay's focus is preserving research and exact draft decisions across those handoffs. -## Obsidian workflow +**First compatibility path: tracker CSV to Relay preview.** In Relay, open **Import a tracker CSV**, choose your file, confirm the company, role, and employer posting URL columns, and preview before saving. Optional status and notes columns are preserved as research. Every new job starts Held; source statuses never approve a draft. This is a file importer, not a tracker account connection or partnership. See the [CSV setup guide](integrations/README.md#tracker-csv--relay) and [fictional example](tests/fixtures/tracker-example.csv). -Select a job, open **Connect your tools**, choose the note purpose and **Create note for selected job**. Edit the downloaded note in your vault, then load it in Relay, review its contents and preview matches before importing. New jobs can start from the downloadable example. Several research notes can be imported together. +### Obsidian -Use **Edit draft in Obsidian** for an application or follow-up draft that returns to the same job version for review. **Download job context** includes source history as a reference snapshot. Research preserves existing status and approval; loading a draft never accepts or sends it. This is an explicit file handoff, with no plugin, vault scanning or background synchronization. +Select a job, open **Connect your tools**, choose the note purpose, and **Create note for selected job**. Edit the downloaded note in your vault, then load it in Relay and preview matches before importing. Use **Edit draft in Obsidian** for a version-bound draft, and **Download job context** for a source-history snapshot. No plugin, vault scanning, or background sync. -[Complete Obsidian guide](integrations/OBSIDIAN.md) | [Architecture and data ownership](ARCHITECTURE.md) +[Complete Obsidian guide](integrations/OBSIDIAN.md) -## ChatGPT and Codex +### ChatGPT and Codex -Choose **Prepare for ChatGPT** or **Prepare for Codex** in **Connect your tools**, share the selected prompt, and return the JSON result for review. Codex can also prepare drafts through its signed-in CLI. [Complete setup and boundaries](integrations/OPENAI.md). +Choose **Prepare for ChatGPT** or **Prepare for Codex** in **Connect your tools**, share the selected prompt, and return the JSON result for review. Codex can also prepare drafts through its signed-in CLI. -## Keeping public pages current +[Complete setup and boundaries](integrations/OPENAI.md) -The project, organization, personal profile and website share one [maintained product description](docs/public-copy.json). [Public-copy process](docs/PUBLIC-COPY.md) explains generation, checks and automatic refreshes. +### GrokCell research templates + +The [GrokCell folder](grokcell/README.md) includes First Principles, Product Ideation, Red Flag, and Garbage Collector. These templates do not connect to Relay or grant access to application records. The [Relay adapter](integrations/GROK_BOT.md) remains the guide for exchanging job research and drafts. See also [context management](context-management/README.md). This is a pinned copy of the MIT-licensed [GrokCell project](https://github.com/sdcarlson/grokcell). ## Run locally @@ -94,7 +104,7 @@ pnpm exec wrangler d1 execute DB --local --config dist/server/wrangler.json --pe pnpm dev ``` -`pnpm dev` binds **http://localhost:3000/** (Vite `strictPort`). Use that URL. Miniflare/workerd may also print an internal `127.0.0.1:NNNN` bind — ignore it for the browser and curl. +`pnpm dev` binds **http://localhost:3000/** (Vite `strictPort`). Use that URL. Miniflare/workerd may also print an internal `127.0.0.1:NNNN` bind - ignore it for the browser and curl. `pnpm start` (after `pnpm build`) binds the built Worker at **http://127.0.0.1:8787/**. @@ -119,17 +129,7 @@ The Sites plugin on `pnpm dev` strips caller-supplied `oai-authenticated-user-*` ## Integration boundaries -The connectors are runnable local commands with file import/export in the app. Notion and Claude require your own credentials. A local assisted trial retrieved real Notion records read-only through the connected Notion tool; that does not validate the standalone Notion command connector. Claude live access has not been tested. Grok Bot uses a documented command/file adapter, not an assumed proprietary API. Bot JSON was transcribed by hand into a validated file and loaded in the browser; fully automatic Bot file transfer is not validated. Browser acceptance, reload, and reimport kept the accepted draft, Ready status, two observations (deduplicated), and review history. There is no automatic background sync, autonomous hunting, application sending, or LinkedIn messaging. Generated claims still require your review. Production deployment has not been validated. This validates a local assisted workflow, not independent user adoption or unattended production. - -## Where Relay fits with existing tools - -Use your preferred discovery and application tools alongside Relay. [Simplify](https://simplify.jobs/) already offers job matching, autofill, resume tailoring, and tracking. Its [Gmail integration](https://help.simplify.jobs/articles/0236686-email-integration) also includes reviewed AI emails and suggested status changes. Relay's focus is preserving research and exact draft decisions across tool handoffs. - -**First compatibility path: tracker CSV → Relay preview.** Simplify documents [CSV import and export](https://help.simplify.jobs/en/articles/2140179-using-the-job-tracker). In Relay, open **Import a tracker CSV**, choose your file, confirm the company, role and employer posting URL columns, and preview before saving. Optional status and notes columns are preserved as research. Every new job starts Held; source statuses never approve a draft or synchronize the application pipeline. Other columns are explicitly listed as omitted. - -This is a file importer, not a Simplify account connection or partnership. CSV handling is tested with fictional fixtures and a Chromium journey covering column selection, preview, import, acceptance, repeat import and reload; a real Simplify export has not yet been validated. Files need posting URLs, comma-separated columns and at most 200 opportunity rows. See the [CSV setup guide](integrations/README.md#tracker-csv--relay) and [fictional example](tests/fixtures/tracker-example.csv). - -Huntr and Teal export compatibility are further candidates, after the first handoff proves useful. Current working integrations and their verification limits are documented in the [setup guide](integrations/README.md). Market positioning was reviewed against vendor documentation on September 5, 2026; repeat use and willingness to pay remain unvalidated. +Connectors are local commands and explicit file import/export. Notion and Claude use your credentials. ChatGPT is a prompt/file handoff; Codex also supports a local CLI adapter; Grok Bot uses a documented command/file adapter. There is no automatic background sync, autonomous hunting, application sending, or LinkedIn messaging. Generated claims still require review. Production deployment and independent user adoption remain separate from this local workflow. ## Checks @@ -137,20 +137,22 @@ Huntr and Teal export compatibility are further candidates, after the first hand pnpm test pnpm exec tsc --noEmit pnpm lint -node tests/api.test.mjs +pnpm public-copy:check ``` -For an existing local database still on migration 0001, apply 0002 from the setup commands. Migration 0002 preserves observations and repairs imported Ready records that lack matching accepted text. Imported Ready is research evidence; a new record stays Held until its exact draft is accepted in Relay. +The project, organization, personal profile, and website share one [maintained product description](docs/public-copy.json). [Public-copy process](docs/PUBLIC-COPY.md) explains generation, checks, and automatic refreshes. + +API checks need a running local server and write only fictional test records. Connector tests mock vendor responses; they do not prove live account access. Domain, import, editor, and API tests cover status preservation, duplicate matching, exact acceptance, stale edits, and authentication rejection. -The last command needs a running local server and writes only fictional test records. Domain, import, editor and connector tests cover status preservation, duplicate matching, imported acceptance, observation identity, editor version conflicts, draft review rules, provider errors and pagination. Connector tests mock vendor responses; they do not prove live account access. API checks verify database read-back, stale edits, exact acceptance, status-preserving follow-up edits and authentication rejection. Local browser and WebMCP reads/import checks were exercised. Preview works before the first import. Browser file import, save and reload preserved source history. Browser acceptance, reload, and post-acceptance reimport preserved the exact accepted draft, Ready status, two observations, and history. The assisted trial ran on `3b1efd7`; a read-only reopen after fast-forward still showed the accepted record on `59ec7ac`. +For an existing local database still on migration 0001, apply 0002 from the setup commands. Imported Ready is research evidence; a new record stays Held until its exact draft is accepted in Relay. ## Hosting and privacy -React/Vinext on Cloudflare Workers with D1 persistence. Local development uses Sites authentication. The production delivery process uses separate staging and production databases with a verified Cloudflare Access gateway; see [hosting and recovery](docs/hosting.md). The checked-in Sites manifest declares logical bindings only. Deploy only the verified release artifact through the protected workflows. Account provisioning, live authentication, and the first production release still require verification before inviting users. +Keep real imports, packets, and draft results in ignored `private-data/`. Keep API keys in environment variables. Local databases, build output, credentials, and personal records stay out of Git. -Keep real imports, packets and draft results in ignored `private-data/`. Keep API keys in environment variables. Local databases, build output, credentials, personal records and the original development Git history are excluded from this release. +Deploy only the verified release artifact through the protected workflows. Account provisioning, live authentication, and the first production release still require verification before inviting users. -Maintained by SyberLabs. Early release: no hiring outcomes, reliability targets or throughput improvements have been established. +Early release: no hiring outcomes, reliability targets, or throughput improvements have been established. ## License diff --git a/docs/PUBLIC-COPY.md b/docs/PUBLIC-COPY.md index 78fa35b..c05731b 100644 --- a/docs/PUBLIC-COPY.md +++ b/docs/PUBLIC-COPY.md @@ -1,6 +1,6 @@ # Keeping Relay's public pages current -**Owner: Seth Carlson, lead engineer.** Update [`public-copy.json`](public-copy.json) when shipped behavior, integration setup, ownership or release status changes. It is the single source for the managed RELAY sections in: +**Owner: Seth Carlson, lead engineer.** Application development credit: Mateo. Update [`public-copy.json`](public-copy.json) when shipped behavior, integration setup, ownership or release status changes. It is the single source for the managed RELAY sections in: - `SyberLabs/relay` - project `README.md` - `SyberLabs/.github` - organization `profile/README.md` diff --git a/docs/public-copy.json b/docs/public-copy.json index 34dd42a..0ca6850 100644 --- a/docs/public-copy.json +++ b/docs/public-copy.json @@ -1,54 +1,56 @@ { "name": "RELAY", "tagline": "Your job search should remember what you've done.", - "summary": "A job-search review workspace that keeps research, application history, and exact accepted drafts together across your tools.", + "summary": "SyberLabs' job-search product: a private review workspace that remembers the roles you researched, the drafts you accepted, and the interviews you started. Assistants help you write; Relay keeps the record.", "repository": "https://github.com/SyberLabs/relay", "leadEngineer": "Seth Carlson", "leadProfile": "https://github.com/sdcarlson", + "peerEngineer": "Mateo", + "peerProfile": "https://github.com/sykosyber", "stage": "Early release", "capabilities": [ - "Consolidate repeated posting URLs while preserving source history.", - "Keep interview notes and follow-ups without resetting application status.", - "Accept an exact draft; changing the wording requires review again.", - "Import a tracker CSV through explicit column mapping and a record preview. Source statuses remain research; existing Relay status and accepted drafts are preserved." + "One history per job: matching posting URLs join the same record, and earlier research stays visible.", + "Exact draft acceptance: you approve specific wording; changing it requires review again.", + "Interview notes and follow-ups that do not reset a submitted or live-loop application.", + "Import a tracker CSV through column mapping and a record preview. Imported statuses stay research; existing Relay status and accepted drafts are preserved." ], "integrations": [ { "name": "ChatGPT", - "description": "Prepared prompts and JSON file handoffs for draft review.", + "description": "Prepare a job packet and prompt, then bring a JSON draft back for review.", "guide": "integrations/OPENAI.md" }, { "name": "Codex", - "description": "Prepared prompts, validated draft files, or local drafting through the signed-in Codex CLI.", + "description": "The same packet, plus optional local drafting through the signed-in Codex CLI.", "guide": "integrations/OPENAI.md" }, { "name": "Obsidian", - "description": "Selected research notes, version-bound draft notes, and job context exports.", + "description": "Selected research notes, version-bound draft edits, and job-context exports from your vault.", "guide": "integrations/OBSIDIAN.md" }, { "name": "Notion", - "description": "Read-only research import through the local command connector.", + "description": "Read-only research import through a local command you run with your own credentials.", "guide": "integrations/README.md" }, { "name": "Claude", - "description": "Draft preparation through the Claude API with your own credentials.", + "description": "Draft preparation from your verified facts through the Claude API, using your own key.", "guide": "integrations/README.md" }, { "name": "Grok Bot", - "description": "Validated research and draft file exchange in the Bot's VM.", + "description": "Validated research and draft file exchange inside the Bot's VM.", "guide": "integrations/GROK_BOT.md" }, { "name": "Tracker CSV", - "description": "Explicit column mapping and preview of a local comma-separated tracker file as research.", + "description": "Map columns, preview rows, and import a local tracker file as research.", "guide": "integrations/README.md" } ], - "boundary": "Integrations require explicit setup or file handoffs. Returned drafts require human review. No automatic application sending or background account sync is included.", - "openaiBoundary": "ChatGPT uses a prompt/file handoff; Codex also supports a local CLI adapter. This release does not include a hosted ChatGPT app or MCP connection." + "boundary": "You stay in control. Integrations are explicit file and command handoffs. Every returned draft needs human review. Relay does not send applications or sync accounts in the background.", + "openaiBoundary": "ChatGPT uses a prompt and file handoff; Codex also supports a local CLI adapter. This release does not include a hosted ChatGPT app or MCP connection." } diff --git a/scripts/sync-public-copy.mjs b/scripts/sync-public-copy.mjs index 52fea7b..87506a0 100644 --- a/scripts/sync-public-copy.mjs +++ b/scripts/sync-public-copy.mjs @@ -23,7 +23,7 @@ const escapeHtml = (text) => export function render(copy, target) { if (!Object.hasOwn(targets, target)) throw Error('Unknown public-copy target.'); - for (const value of [copy.repository, copy.leadProfile]) { + for (const value of [copy.repository, copy.leadProfile, copy.peerProfile]) { const url = new URL(value); if ( url.protocol !== 'https:' || @@ -37,7 +37,7 @@ export function render(copy, target) { } const guide = `${copy.repository}/blob/main/integrations/OPENAI.md`; const integrations = copy.integrations.map((item) => item.name).join(', '); - const credit = `**Lead engineer: [${copy.leadEngineer}](${copy.leadProfile}).**`; + const credit = `**Lead engineer: [${copy.leadEngineer}](${copy.leadProfile}).** Application development: [${copy.peerEngineer}](${copy.peerProfile}).`; if (target === 'project') return `**${copy.tagline}** diff --git a/tests/public-copy.test.mjs b/tests/public-copy.test.mjs index 123e042..3afcefe 100644 --- a/tests/public-copy.test.mjs +++ b/tests/public-copy.test.mjs @@ -15,6 +15,23 @@ void test('every advertised integration has a checked-in setup guide', async () for (const item of copy.integrations) await access(new URL('../' + item.guide, import.meta.url)); assert.equal(copy.leadEngineer, 'Seth Carlson'); + assert.equal(copy.leadProfile, 'https://github.com/sdcarlson'); + assert.equal(copy.peerEngineer, 'Mateo'); + assert.equal(copy.peerProfile, 'https://github.com/sykosyber'); +}); + +void test('project and organization copy credits both maintainers', () => { + for (const target of ['project', 'organization']) { + const content = render(copy, target); + assert.match(content, /Lead engineer: \[Seth Carlson\]\(https:\/\/github.com\/sdcarlson\)/); + assert.match( + content, + /Application development: \[Mateo\]\(https:\/\/github.com\/sykosyber\)/, + ); + } + const profile = render(copy, 'profile'); + assert.match(profile, /Lead engineer/); + assert.doesNotMatch(profile, /Application development/); }); void test('sync preserves all content outside its block and is idempotent', () => { @@ -47,7 +64,7 @@ void test('website product data is escaped before rendering', () => { }); void test('public links reject executable schemes, other hosts and embedded credentials', () => { - for (const field of ['repository', 'leadProfile']) { + for (const field of ['repository', 'leadProfile', 'peerProfile']) { for (const value of [ 'javascript:alert(1)', 'data:text/html,test',