#263 · Document one public-source-to-community-knowledge walkthrough
Last checked with GitLab: . Status comes from GitLab using a 2-minute cache. Merge events clear affected cached statuses. An already-open page does not update itself. Refresh page.
An MR completes this bounty when it is merged into main with Closes #263 and GitLab closes the issue. A mention or an updated timestamp is not completion. Awarded points appear in Activity.
cp .dev.vars.example .dev.vars && pnpm dev, after rebasing on main) and fully test your change before opening the MR.
Description
The operationalization plan links knowledge services and implicit tasks, while research templates still emphasize external collaboration links. Show how a member can use the actual existing services through one manual, consent-aware workflow.
Who might enjoy this
- Community interests: Community / knowledge sharing, Research, Full stack, Privacy
- Skills: docs, ux
- Experience: starter; work style: writing.
- Readiness: ready; bounty size: S (existing points tier; standard merge award stacks separately).
Current behavior and starting points
Source-reviewed against main cf05b29c6256dba70d0ebc09b22cc9867cdb786a on2026-10-18. Check current main and related issues/MRs before implementing so existing work is reused.
Relevant Files
- apps/wiki/src/content/docs/research/research-template.md
- apps/wiki/src/content/docs/research/research-tasks.md
- docs/plans/2026-03-07-community-operationalization-design.md
- apps/fieldnotes/src/index.ts
- apps/qa-form/src/templates/question-detail.ts
- apps/task-exchange/src/templates/task-form.ts
Deliverables
- A concise guide following a synthetic public-source note into a Field Notes draft, a reviewed canonical wiki change, an unresolved Q&A question and a well-scoped follow-up task.
- An editable text/diagram checklist showing who reviews each handoff, audience restrictions and what counts as completion at each service.
Dependencies and decisions
No prerequisite issue is required. Re-read current main and linked MRs before starting.
Acceptance criteria
- [ ] Rehearse the workflow locally with synthetic content; record actual route names and visible states, including pending review and an unanswered question.
- [ ] Explain that Q&A answers and private/community notes are not automatically public; handoffs are member-approved and contain attribution.
- [ ] A newcomer can choose one entry point without reading every service manual; wiki check/build pass.
- [ ] Record named baseline failures and the exact commands used. A behavior fix includes a real route/database/protocol check observed failing before the change. Knowledge work includes source traceability and reproducible reviewer evidence.
- [ ] Run the affected app's existing checks. Explain any baseline failures rather than reporting a matching failure count as proof.
Try it locally
Start from the existing source files above. The following is the target demo your contribution should enable; a newly proposed script or fixture is part of the deliverable:
Use a fictional public lab note with one unanswered question and decide which service should own each next step.
Use public or synthetic examples. Starter work should run without production access; explicitly name any software/device prerequisite before claiming it is ready.
Out of scope
- No new cross-service automation, no auto-publication, no duplicate bounty/task awards, no generic architecture diagram (#236) or release-note template (#248).
- Unrelated refactors, new services/providers, bulk dependency changes, production access changes, unrequested notifications, and copying private member material. Keep credentials and unresolved security findings outside the issue and repository.
For a coding agent and reviewer
Read AGENTS.md, applicable .cursor/rules/, app instructions and docs/contributing/agentic-bounty-review.md. Reuse the existing shared helpers, identity/access paths and app styling. Implement one bounded story and provide evidence the accepting app maintainer can reproduce. State updated / pre-release verified / released / live verified accurately.
A parent index carries no duplicate award for these child deliverables. Open one scoped MR using this issue's actual number after the closing keyword. Link your GitLab identity on Scoreboard; the existing merge webhook handles eligible points.
Catalog index: #258.
<!-- community-interest-bounty:2026-10-18:wiki-knowledge-contribution-walkthrough -->
Relevant files
-
[apps/wiki/src/content/docs/research/research-template.md](https://git.juntogroups.org/irregulars/irregularchat-monorepo/-/blob/main/apps/wiki/src/content/docs/research/research-template.md)from issue -
[apps/wiki/src/content/docs/research/research-tasks.md](https://git.juntogroups.org/irregulars/irregularchat-monorepo/-/blob/main/apps/wiki/src/content/docs/research/research-tasks.md)from issue -
[docs/plans/2026-03-07-community-operationalization-design.md](https://git.juntogroups.org/irregulars/irregularchat-monorepo/-/blob/main/docs/plans/2026-03-07-community-operationalization-design.md)from issue -
[apps/fieldnotes/src/index.ts](https://git.juntogroups.org/irregulars/irregularchat-monorepo/-/blob/main/apps/fieldnotes/src/index.ts)from issue -
[apps/qa-form/src/templates/question-detail.ts](https://git.juntogroups.org/irregulars/irregularchat-monorepo/-/blob/main/apps/qa-form/src/templates/question-detail.ts)from issue -
[apps/task-exchange/src/templates/task-form.ts](https://git.juntogroups.org/irregulars/irregularchat-monorepo/-/blob/main/apps/task-exchange/src/templates/task-form.ts)from issue
Hints
No hints yet.
Activity
No points have been awarded for this bounty yet.
Comments
Sign in to join the discussion.
No comments yet. Be the first to weigh in.