Useful work only — it must help a real person.
[about]
how to work together
collaborating brief, working map, availability. credentials live on the cv.
I write how-tos a tired first-time user can finish. Quiet reflection before visible action — a delayed reply is often the work, not a freeze. Bring the tangled problem early, with the rationale attached. Credentials live on the CV. Availability, and how to work together, live here.
Communication
Discord
Style
Written first · conclusion, then evidence
Energy
Pacer · peak early–mid morning
Focus
Protected blocks · written checkpoints
Useful, kind work that still helps when the world is loud.
Quiet against noise — focus protected from the always-on world.
Human hands, human yes — AI helps; people lead and approve what ships.
Written for loud minds — docs that respect brains that do not sit still.
Open tools, sealed work — share what we can; some things stay private on purpose.
Collaborating
Thoughtful structure with room to adapt. I sort complicated technical work into a few workable paths, then rearrange when the evidence changes. Meaningful outcomes, sound reasoning, and care for teammates matter together.
Do
- Lead with the conclusion, then the reasoning and evidence.
- Share drafts early, before the solution is hard to reshape.
- Set decision dates that protect analysis without postponing action.
- Name what is working before the gaps, risks, or defects.
- Invite a direct view in a smaller setting and leave time to finish.
Avoid
- Springing urgent requests without priority, impact, or timing.
- Treating careful questions as resistance or lack of commitment.
- Adding meetings when a written update would suffice.
- Leaving disagreement unspoken until it has already curdled.
- Selling an idea on enthusiasm while omitting evidence and tradeoffs.
Harmony versus a clear technical position
I can see why several viewpoints make sense and may soften a disagreement to keep the room comfortable, even when a firm technical concern is forming. Ask what concern I would want recorded before this ships.
Thoroughness versus timely delivery
There is a pull to understand the full picture and meet a high internal standard, paired with knowing the team cannot wait for perfect certainty. Set a time boundary and ask which evidence is enough to proceed today.
Under pressure
- What you'll see
- I may withdraw into research, revisit details, or quietly absorb extra work to preserve harmony. A delayed response is usually processing, not disengagement.
- What helps
- Cut the list to the essential work and state what can wait. Name concerns directly and calmly, then leave focused time to regroup.
Feedback
- Giving me feedback
- Direct, specific, with examples, impact, and a practical next step — writing or a calm one-to-one. Leave processing time. Connect it to quality and team outcomes; do not turn disagreement into a competence judgment.
- How I give it
- Thoughtful and candid, aimed at facts, standards, and improvement. Keep the substance. If it lands cool, ask for the human impact. Treat my questions as an effort to understand the work.
How I might annoy you
- Extra research after a sound path exists
- Thoroughness is the default. I will keep verifying unless you set a decision date.
- Quiet processing
- A delayed reply is often the work, not a freeze. Hyperfocused and quiet does not mean upset.
- Softened disagreement
- I may hold a technical concern to keep collaboration comfortable. Ask what I would want recorded before this ships.
- Harmony tax
- Under pressure I absorb extra work or withdraw into research rather than escalate.
How you might annoy me
- Surprise urgency
- Do not spring a request without priority, impact, or timing.
- Questions treated as resistance
- Careful questions are how I commit, not how I stall.
- Meetings that could be a message
- A written update beats another call. Protect the calendar.
- Enthusiasm without evidence
- Do not sell a path on vibe while omitting tradeoffs.
- Unspoken disagreement
- Name the gap before it curdles.
- Interruptions with no notice
- Unplanned shifts make focus expensive to regain. Say what changed, why, and what is still fixed.
I might need help with
- Cutting the list
- Tell me what can wait. I will otherwise try to finish all of it.
- A decision date
- Protect analysis time, then stop postponing action.
- Enough evidence for today
- Ask which proof would be enough to proceed — then ship that slice.
- Context before the meeting
- Send background and distinguish an initial reaction from a final decision.
- Asking for help
- I will try to solve it myself first. A calm, specific ping lands better than a pile-on.
I love
- Tangled problems, early
- Bring the mess while several options are still available. Arranging is the work.
- Rationale attached
- Constraints, evidence, and root cause before you ask for commitment.
- Purpose and people impact
- Name who it helps and why it is worth the care.
- Written checkpoints
- Clear deliverables and a next check-in. Status theatre is optional.
- Kind, specific feedback
- Examples, impact, a next step. In writing or a quiet one-to-one.
- Writing that a tired user can finish
- Turning a messy Slack thread into a page someone can complete.
Working map
Cloverleaf collaborating brief, 24 Aug 2026. A starting point, not a box.
Energy rhythm
Pacer
- Peak · early–mid morning
- Trough · early–mid afternoon
- Recovery · late afternoon–early evening
16 types
Inspector
- Introversion 80
- Sensing 55
- Thinking 75
- Judging 65
DISC
CD · Designer
- Conscientiousness 78
- Dominance 63
- Steadiness 42
- Influence 7
Enneagram
9 · Peacemaker
- Wing · 1 Reformer
- Growth · 3 Achiever
- Stress · 6 Loyalist
- Triad · Gut
Instinctive drives
I.D. 6572
- Complete 7
- Verify 6
- Authenticate 5
- Improvise 2 · avoid
CliftonStrengths
Executing
- Arranger
- Belief
- Woo
- Analytical
- Context
VIA
Transcendence
- Kindness
- Humor
- Love of learning
- Hope
- Judgment
recognition
Human-Focused AI Award
Tetrate Buildathon — selected from 170+ applicants
"NeuroShell puts AI to work while centering real human value."
— Birger Moëll, Associate Professor in Computational Linguistics, Uppsala University
Availability
Availability
Remote · globalSeeking an async remote IC role worldwide in technical writing, accessible frontend, or IT support. AEWV-accredited employers in New Zealand are welcome; they are not required.
- Role match
- Technical Writer · Accessible Frontend · Remote Technical Support
- Relocation
- On the ground in Auckland Dec 2026–Feb 2027 for in-person meetings · full NZ relocation in 2027 if an offer funds it
- Mobility
- NZ eTA approved · Australian business visitor visa approved · overlapping hours with US, Oceania, and EU teams
Employer due-diligence pack
- Formal dated CV and employment chronology — five role-targeted PDFs on the CV
- Selected how-tos, READMEs, and shipped public work on the projects page
- Public writing at darkheartlabs.technology/writing
- Identity, qualification, and immigration documents on request
A formal evidence pack is available for employer due diligence and the immigration process.
CV — skills inventory · PDFs → Projects — selected work →
Official Immigration New Zealand AEWV process ↗If you're being quiet it means you're thinking. If I'm being quiet it means I'm in flow. Ping me on Discord — I promise I'll resurface.
— JV · Dark Heart Labs.