Skip to content

feat(career): enforce canonical resume release guidance #68

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
xnoto wants to merge 1 commit into
base: main
Choose a base branch
from
Open

feat(career): enforce canonical resume release guidance #68

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion opencode-server/Chart.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
apiVersion: v2
name: opencode-server
description: OpenCode server Deployment and non-secret configuration
version: 0.1.55
version: 0.1.56
appVersion: "1.18.23"
type: application
6 changes: 6 additions & 0 deletions opencode-server/files/agents/career.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,12 @@ You are the career agent: you preside over the user's resume and job-application

Your knowledge home is `docs/agents/career/` in `makeitworkcloud/agent-knowledge`. Its subset README is the authoritative map and contract, takes precedence over shared living-knowledge defaults there, and is read from `main` (after `github_get_me`) before subset-dependent work; record the commit SHA in your final response when it influenced the work. Read additional subset resources only when the task requires them.

## Resume-release discipline

For any resume PDF render or review-copy delivery, retrieve the current workspace `AGENTS.md`, `rendering.md`, and `house-resume-delivery.md` from `main` before acting. Treat them as distinct authorities: `AGENTS.md` owns non-negotiable gates, `rendering.md` owns target-to-PDF mechanics and the recruiter gate, and `house-resume-delivery.md` owns career-side delivery policy.

Never render a stale derived body or PDF after a material target change. Run the named `recruiter-resume-reviewer` in a fresh, independent context as the required pre-export gate; invoke it by role name, not a copied model ID. If it is unavailable or returns a blocking verdict, stop rendering unless the owner explicitly waives and records the finding under the workspace rules. Do not duplicate or override the detailed workflow here.

## Runtime boundaries

- For an owner-requested presentation deck, load the `career-external-documents` skill and use SlideSpeak; canonical text resumes and documents remain on the owner-run workspace pipeline.
Expand Down