mantoshkumar1 / mantoshkumar1/mantoshkumar1.github.io
Audit public work-authorization claims for exact recruiter-facing accuracy
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 0
- Avg merge
- 13m
- Merged PRs (30d)
- 2
Description
Priority: High
Problem
The homepage, résumé, and contact surfaces make explicit public work-authorization claims. Because these are recruiter-facing legal/employment facts, wording must be exact, supportable, and consistent across every page and knowledge source.
Goal
Verify the legally supportable work-authorization wording and make it one authoritative public fact across the website and Ask Mantosh knowledge.
Scope
- Inventory every public occurrence of citizenship/work-authorization wording.
- Verify the exact jurisdictions and conditions that can be claimed without qualification.
- Distinguish citizenship, existing work authorization, visa-free business travel, and future sponsorship eligibility where relevant; do not conflate them.
- Update homepage, experience/resume/contact pages, structured metadata, and Ask Mantosh canonical profile knowledge if needed.
- Add a deterministic content check if practical so the wording cannot drift across surfaces.
Acceptance criteria
- Every public work-authorization statement has been reviewed against authoritative personal/legal evidence.
- One canonical wording is documented.
- All public pages and Ask Mantosh sources use consistent wording.
- No page implies broader authorization than can be substantiated.
- Future drift is prevented by documentation or an automated check where practical.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Inventory work-authorization wording across the homepage, résumé, contact surfaces, structured metadata, and Ask Mantosh canonical profile knowledge. Start by comparing each statement with authoritative personal or legal evidence and document one supportable canonical wording. Done means every public source uses consistent wording without implying broader authorization, with a drift-prevention check or documentation where practical.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- content, documentation, web-dev
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100