Live Jira/Confluence onboarding and portfolio audit — 2026-07-07

# Live Jira/Confluence onboarding and portfolio audit — 2026-07-07

AI Summary

Purpose:

• Preserve the public-safe findings from a live Jira/Confluence MCP audit for onboarding and portfolio updates.

Key points:

• Confluence DT has a 9-page Labrador onboarding set: roadmap, environment setup, codebase, domain knowledge, development workflow, deployment/operations, first-ticket guide, personal onboarding journal template, and mentoring checklist.
• Jira DAT-3295 records the completed 2026-07 documentation package for 12 library crawler ecosystems: onboarding guide + improvement-history page per ecosystem.
• Confluence also has a Google Docs management policy page defining when Google Docs/Sheets should be used, how they should be linked from Confluence, and naming/layout constraints.
• No secrets, tokens, credentials, private hostnames, or raw internal operational values are preserved here.

Relevant when:

• Updating onboarding hub copy, technical portfolio items, team documentation governance, or crawler-modernization narrative.

Do not read full document unless:

• You need the live-audit evidence behind the 2026-07-07 portfolio/onboarding updates.

Linked documents:

• ai/wiki/projects/confluence-lib-onboarding-docs.md
• ai/wiki/projects/library-missing-improvements.md
• human/portfolio/items/crawler-modernization.html
• human/portfolio/items/team-doc-governance.html
• human/portfolio-todo.md

Details

Confluence — Labrador onboarding set

Live page checked:

• DT / 래브라도 온보딩 (pageId=4140957726, version 5)

Observed structure:

• 30/60/90-day style onboarding, with the current stated goal that core onboarding is completed in the first month and the next two months are deepening / independent-contribution periods.
• Completion criteria:

- Local independent build/test/debug ability. - Independent first-ticket handling through PR.

• Page set under the onboarding parent:

1. 1. 온보딩 로드맵 (pageId=4140859477) 2. 2. 개발 환경 세팅 (pageId=4140957792) 3. 3. 코드베이스 구조 (pageId=4141088875) 4. 4. 도메인 지식 (pageId=4141023365) 5. 5. 개발 워크플로우 (pageId=4141318151) 6. 6. 배포 및 운영 (pageId=4141449217) 7. 7. 첫 티켓 가이드 (pageId=4141416452) 8. 8. 온보딩 개인 페이지 템플릿 (pageId=4151443613) 9. 9. 온보딩 멘토링 체크리스트 (pageId=4156063758)

• Roadmap emphasizes:

- Week 1: local environment + product installation/use, scan execution, report review. - Week 2: build/test, JUnit 5, CI flow, one unit test. - Weeks 3–4: SCA/CVE/SBOM/VEX/BSCA, module map, CVE end-to-end trace. - Month 2: first ticket from assignment to PR merge. - Month 3: medium-complexity ticket + peer PR reviews + KPI draft.

• The personal onboarding journal template captures weekly work, good points, improvements/questions, monthly deliverables, first-ticket reflection, 90-day reflection, and final checklist.

Portfolio/onboarding use:

• Good source for the team-doc-governance item because it proves the documentation standard became an actual onboarding operating system, not just naming cleanup.
• For public portfolio, avoid page IDs/URLs and keep details generalized.

Jira — library missing-data documentation package

Live issue checked:

• DAT-3295 — [DOC|LIB] 라이브러리 누락 개선 전체 문서화
• Status: completed.
• Created: 2026-07-02, updated: 2026-07-04.

Observed scope:

• Parent issue records a completed documentation package for 12 language/registry ecosystems.
• Each ecosystem has two Confluence artifacts: onboarding guide and improvement-history page.
• Ecosystems listed:

- JavaScript / npm - Python / PyPI - PHP / Packagist - Ruby / RubyGems - Go / Go Modules - Java / Maven - C# / NuGet - Swift / CocoaPods - Swift / Swift Package Index - C/C++ / Conan - C/C++ / vcpkg - C/C++ / Hunter

• Jira search also returned the 12 child tasks DAT-3299–DAT-3310, each completed and tied to one ecosystem's onboarding/improvement-history docs.

Portfolio/onboarding use:

• Reinforces crawler-modernization with concrete documentation/operationalization: not only code/data fixes, but a completed 12-ecosystem onboarding + improvement-history knowledge base.
• Avoid exposing internal Jira IDs on public pages unless the page is explicitly internal; use “12개 생태계” instead.

Confluence — Google Docs/Sheets document management policy

Live page checked:

• DT / Google Docs 문서 관리 (pageId=1868333076, version 3)

Observed policy:

• Google Docs is reserved for frequently updated documents or architecture/diagram-heavy material.
• Google Docs documents should be referenced from Confluence pages rather than becoming disconnected standalone sources.
• Directory layout follows target > category, for example component/library/file/function/license/vulnerability/crawler categories.
• Document prefixes follow the directory structure, with examples like component/library/crawler or component/file/survey-style names.
• Constraints include max directory depth 2, short prefixes, and a recommendation to split spreadsheets when a workbook exceeds 5 sheets.

Portfolio/onboarding use:

• Reinforces the team-doc-governance item: documentation policy covered not just Jira/Confluence naming, but also Google Docs/Sheets boundaries and discoverability.
• For public copy, say “Google Docs/Sheets 사용 기준과 Confluence 링크 규칙” rather than exposing folder links.

Sanitization notes

• Credentials, internal tokens, hardcoded PAT values, DB credentials, and host connection details were not copied.
• Page IDs and Jira issue IDs are retained only in this AI source for traceability; human-facing public pages should generalize them.