First-external-contributor door is open (one-PR asks)

[enricopiovesan]

We published a short, honest writeup on opening a small first-contributor door — not a metrics launch:

The first external contributor door — without the hype

Still open, sized for one PR

• traverse#1361 — minimal TypeScript consume of traverse-embedder-web
• traverse#1362 — honest Python CLI subprocess example (real verbs only)
• registry#485 — publish small text.slugify through the normal registry path

All labeled help wanted / good first issue / no-spec-needed.

Comment on the issue you want, keep the PR to the done-when, and wait for CI. CLA and governing-spec fields still apply — the door is small on purpose so the gates stay real.

Related earlier list (broader set): Discussion #1364.

[enricopiovesan]

Three more one-PR asks (same shape as the list above):

• traverse#1377 — docs honesty: fix traverse-embedder-web "published on npm" drift (package README vs live npm / Example: minimal TypeScript consume of traverse-embedder-web (one PR) #1361/docs: add minimal TypeScript consume example for traverse-embedder-web #1375)
• traverse#1378 — minimal browser FetchBundleLoader consume example (pairs with Node consume-typescript)
• registry#486 — publish small text.truncate (separate from slugify #485)

All labeled help wanted / good first issue / no-spec-needed (registry also enhancement + documentation).

[enricopiovesan]

Registry help-wanted batch (2026-09-14 evening)

Examples are still the on-ramp; graduating to a published capability is the next step. Registry is ready for that; apps are not the ask here.

Status	Issue	Capability
Open / unclaimed	registry#485	text.slugify
Claimed — PR open	registry#486 → PR #487	text.truncate
New	registry#488	text.normalize-whitespace
New	registry#489	text.extract-urls
New	registry#490	json.pick-keys

Each ticket is one-PR-wide: contract + capability-src/ + publish checklist, labeled help wanted / good first issue / enhancement / no-spec-needed. Comment to claim; keep PRs separate (do not bundle).

Not hype — just a clear batch if you want to learn the real registry path without inventing a domain model.

[enricopiovesan]

Registry help-wanted batch — business / agent-governance capabilities (2026-09-14)

Apps are not ready — these asks are capabilities only. No generic string/json utilities. Agent proposes; capability/runtime decides.

Two tracks:

Specified (well-defined contracts) — 10

Sized like prior one-PR publishes; labeled help wanted / good first issue / enhancement / no-spec-needed. Names checked against the published catalog (distinct from text.redact-entities, core.authorize, core.calculate-price, retention.eligibility-classify, uncertainty.score, support.ticket-sla-breached).

Issue	Capability
registry#493	core.redact-for-export — policy-shaped PII/secret redact-before-export
registry#494	core.eligibility-check — deterministic rule-table eligibility
registry#495	core.quote-with-caps — formula quote + hard caps
registry#496	core.check-declared-permission — thin authz from declared roles/permissions
registry#497	core.risk-band — risk band from structured signals
registry#498	core.extract-to-schema — extract into fixed schema (fail closed)
registry#499	core.content-policy-gate — allow/deny/revise for agent output
registry#500	core.consent-purpose-check — consent / purpose binding
registry#501	core.ttl-expiry-decide — TTL / expiry decision
registry#502	core.idempotency-guard — business duplicate-submit guard

Creative-with-guardrails — 5

Same publish path + machine-readable contract + tests. Titles marked CREATIVE. Must be deterministic or fail-closed with explicit uncertainty — no silent LLM invent, not a thin LLM string wrapper, not a generic util. Labeled help wanted / enhancement / no-spec-needed (more design judgment than the specified list, so not tagged good first issue).

Issue	Capability
registry#503	core.dispute-triage-classify
registry#504	core.refund-eligibility-decide
registry#505	core.vendor-risk-questionnaire-score
registry#506	core.sla-outcome-classify
registry#507	core.invoice-line-normalize

Comment on the issue to claim it; one capability per PR; branch from origin/main. Follow CONTRIBUTING.md + coverage gates.

[enricopiovesan]

Welcome to the folks who showed up this week — @Morrowga, @Rayan-and-beyond, @ege-arhan, @EthemKD, and anyone else poking around. Fresh help-wanted batch on business / agent-governance capabilities: traverse-framework/registry#493 through traverse-framework/registry#507. If Traverse has been useful, a star on https://github.com/traverse-framework/traverse helps others find it — optional, no pressure.

[enricopiovesan]

New initiative: print-support capability pack

We opened a registry initiative for a manufacturing-shaped capability pack: governed designed-in print support (mesh codecs, overhang analysis, orientation scoring, breakaway fins, sway braces, export gate, bed pad).

Value is still discover → execute → trace — agents must not freestyle scores, fin geometry, or “safe to export.”

Umbrella

• registry#596 — Initiative: print-support

Help wanted (one capability per PR)

Issue	Capability	Notes
#597	print.mesh-parse	STL/3MF → mesh IR
#598	print.mesh-write	mesh IR → STL/3MF
#599	print.overhangs-analyze	overhangs + bed reachability
#600	print.orientation-score	good first issue
#602	print.fins-generate	breakaway fins
#601	print.sway-braces-generate	tall-part braces
#603	print.export-gate	good first issue
#604	print.bed-pad-generate	v1 bbox pad

All labeled help wanted · enhancement · no-spec-needed (plus good first issue where noted).

Rules of the door

• Capability pack only — apps are not ready; no app rewrite PRs
• Fork + PR; one capability per PR; human review; registry CI gates
• Today’s execution boundary is stdin/stdout JSON (no ambient filesystem)
• Skill path welcome: traverse-capability-author
• Domain inspiration only (e.g. Support Fins / Slant3D technique) — do not copy third-party source

Comment on the issue you want, keep the PR to the done-when, wait for CI.

[enricopiovesan]

Clarification: “apps not ready” ≠ leave domain logic in the host

Quick door note for anyone claiming a help-wanted ticket:

• Capabilities are the home of non-UI business logic — pricing, eligibility, consent, codecs, scorers, generators, export gates. Hosts/clients do UI + I/O only.
• “Apps are not ready” means do not open a PR that ports a whole product shell / UI app into these repos. It does not mean “keep domain rules in JS forever” or “Traverse is only tiny utils.”
• “One small capability” = one concern per package, not a size ceiling. Utility-tier helpers teach the publish pipeline; preferred publishes are business-shaped.
• Living example of a domain pack (capabilities only): print-support initiative #596 · Announcement #1540.

Corpus fix for cold readers is tracked on the site (website#124); same discover → execute → trace pitch as always.