Keputusan engineering
Ada 49 keputusan arsitektur yang tercatat. Delapan keputusan berikut paling menjelaskan repositori ini.
- ADR-005Build One Immutable Documentation Platform
Satu objek platform immutable menjadi tulang punggung yang dibaca oleh semua alat dokumentasi.
- ADR-019Introduce a Documentation SDK
Satu SDK tingkat tinggi menjadikan paket internal sebuah produk yang siap dipakai pihak lain.
- ADR-036Adopt a Vertical Slice Strategy
Produk dibangun utuh sebagai vertical slice, bukan lapis demi lapis.
- ADR-037Prefer Delayed Extraction Across Vertical Slices
Kode bersama baru diekstrak setelah produk kedua benar-benar membutuhkannya.
- ADR-038Prefer Capability Extraction Over Framework Extraction
Yang dibagikan adalah kapabilitas seperti storage dan search, bukan kode framework.
- ADR-044Introduce Runtime Independence Validation
Kemandirian dari runtime tertentu diuji dengan layanan nyata, bukan sekadar diasumsikan.
- ADR-048Introduce Framework-Neutral Design Tokens
Konsistensi visual dibangun dari token yang tidak terikat framework, bukan dari pustaka komponen bersama.
- ADR-049Introduce a Derived Repository Atlas
Atlas ini menurunkan inventarisnya dari repositori alih-alih memelihara salinan.
Tidak ada keputusan yang cocok dengan filter ini.
| ID | Judul | Diputuskan | Status |
|---|---|---|---|
| Fondasi dan ekosistem dokumentasi | |||
| ADR-001 | Centralize Documentation Infrastructure in a Framework-Agnostic PackagePlace reusable documentation parsing, validation, and models in one stable workspace package.Milestone: M1.2 | diterima | |
| ADR-002 | Keep the Document Registry as an InventoryDiscover, collect, and expose parsed documents without interpreting their relationships or presentation.Milestone: M1.3 | diterima | |
| ADR-003 | Resolve Only Declared Metadata RelationshipsDerive forward references and backlinks from canonical metadata without changing the Document Registry or inspecting Markdown content.Milestone: M1.4 | diterima | |
| ADR-004 | Use Deterministic Search over the Document RegistryBuild framework-agnostic field search from canonical registry entries with explicit ranking and stable ordering.Milestone: M1.5 | diterima | |
| ADR-005 | Build One Immutable Documentation Platform PilihanCentralize lifecycle orchestration while preserving the responsibilities of Registry, Reference Resolution, and Search.Milestone: M1.6 | diterima | |
| ADR-006 | Make the Knowledge Hub a Documentation Platform ConsumerRemove application-owned documentation infrastructure and keep the Knowledge Hub focused on presentation.Milestone: M1.7 | diterima | |
| ADR-007 | Expose Documentation through a Read-Only Repository CLIAdd an independent terminal application that consumes the Documentation Platform without introducing documentation logic.Milestone: M2 | diterima | |
| ADR-008 | Version Structured Repository CLI OutputExpose Documentation Platform results as a stable, versioned JSON contract while preserving text as the default.Milestone: M2.1 | diterima | |
| ADR-009 | Separate Documentation Quality Linting from Structural ValidationEvaluate repository quality conventions in a reusable linter that consumes the Documentation Platform independently from the CLI.Milestone: M2.2 | diterima | |
| ADR-010 | Export Documentation Platform Snapshots as Static JSONGenerate deterministic offline artifacts in a separate read-only application that consumes one Documentation Platform.Milestone: M2.3 | diterima | |
| ADR-011 | Stabilize Documentation Package Entry PointsDefine versioned root package APIs while keeping implementation modules and delivery schemas independently evolvable.Milestone: M2.4 | diterima | |
| ADR-012 | Consume Stable Documentation APIs in VS CodeAdd a read-only editor application that delegates documentation knowledge and quality evaluation to the stable package roots.Milestone: M2.5 | diterima | |
| ADR-013 | Ground AI Services in the Documentation PlatformAdd a provider-independent interpretation layer whose prompts and normalized responses remain grounded in canonical Platform data.Milestone: M2.6 | diterima | |
| ADR-014 | Keep Documentation Recommendations DeterministicRank repository-implied document relevance with explicit reproducible rules while leaving explanation to the AI service layer.Milestone: M2.7 | diterima | |
| ADR-015 | Centralize Documentation ConfigurationDefine one strict repository-owned configuration contract shared by every documentation consumer.Milestone: M2.8 | diterima | |
| ADR-016 | Resolve Documentation Configuration OnceShare one immutable, source-aware policy object across every documentation package and application.Milestone: M2.9 | diterima | |
| ADR-017 | Prepare Documentation Packages for External DistributionTreat reusable documentation packages as validated release units while keeping applications private.Milestone: M3.0 | diterima | |
| ADR-018 | Validate Documentation Packages Through an External ConsumerProtect public package contracts with a tracked third-party-style integration fixture.Milestone: M3.1 | diterima | |
| ADR-019 | Introduce a Documentation SDK PilihanProvide one recommended façade for common external workflows while preserving specialized packages.Milestone: M3.2 | diterima | |
| ADR-020 | Manage Documentation Package VersionsUse independently versioned Changesets plans for documentation packages and their internal dependency graph.Milestone: M3.3 | diterima | |
| ADR-021 | Introduce Documentation Extension ContractsExpose a small set of typed integration contracts without introducing runtime plugin infrastructure.Milestone: M3.4 | diterima | |
| ADR-022 | Dogfood the Documentation SDKMake the Knowledge Hub an SDK-only first-party consumer and protect that public package boundary.Milestone: M4.0 | diterima | |
| ADR-023 | Standardize Repository BootstrapProvide a conservative SDK helper that creates a valid documentation environment without creating or overwriting repositories.Milestone: M5.0 | diterima | |
| ADR-024 | Define Documentation CI ContractExpose deterministic documentation validation orchestration without coupling the ecosystem to an automation provider.Milestone: M5.1 | diterima | |
| ADR-025 | Introduce Documentation DoctorSeparate deterministic remediation guidance from validation through a read-only SDK diagnostic engine.Milestone: M5.2 | diterima | |
| ADR-026 | Introduce Repository Health AssessmentProvide deterministic, informational maintainability metrics over an existing Documentation Platform without creating validation or grading semantics.Milestone: M5.3 | diterima | |
| ADR-027 | Standardize Package Release WorkflowCoordinate versioning, existing verification, deterministic artifacts, and release review without coupling preparation to publication or a registry.Milestone: M6.0 | diterima | |
| ADR-028 | Add npm Publication ReadinessAdapt registry-independent release artifacts to safe, explicit, read-only npm readiness without exposing publication through the SDK.Milestone: M6.1 | diterima | |
| ADR-029 | Build the Documentation Website on the Public SDKMake the official product documentation a first-party reference consumer of the stable documentation SDK.Milestone: M6.2 | diterima | |
| ADR-030 | Derive the Documentation Graph as a Deterministic VisualizationVisualize existing Registry and Reference Resolver information without creating a second graph data source.Milestone: M6.3 | diterima | |
| ADR-031 | Introduce Documentation Compatibility AnalysisAssess explicit platform targets through deterministic read-only rules without coupling compatibility to migration execution.Milestone: M6.4 | diterima | |
| ADR-032 | Documentation Upgrade PlanningKeep upgrade planning deterministic and read-only by deriving every step from an existing compatibility report.Milestone: M6.5 | diterima | |
| ADR-033 | Documentation Upgrade VerificationCompare preserved upgrade plans with current compatibility and explicit evidence through a deterministic, read-only verification model.Milestone: M6.6 | diterima | |
| ADR-034 | Adopt a Release-Candidate Acceptance ProcessRequire supported-runtime, public-contract, external-consumer, performance, security, accessibility, and release-rehearsal evidence before release.Milestone: M7.0 | diterima | |
| ADR-035 | Define Browser, Platform, and CLI Acceptance BoundariesRequire runtime browser and Linux evidence while keeping Windows, warnings, CLI distribution, and live publication claims explicit.Milestone: M7.0, M7.1 | diterima | |
| Vertical slice produk | |||
| ADR-036 | Adopt a Vertical Slice Strategy PilihanValidate product architecture with one complete notes feature path.Milestone: M8.0 | diterima | |
| ADR-037 | Prefer Delayed Extraction Across Vertical Slices PilihanKeep Fieldnotes and Fieldmarks independent until reuse is proven.Milestone: M8.1 | diterima | |
| ADR-038 | Prefer Capability Extraction Over Framework Extraction PilihanPromote proven mechanics while preserving independent product slices.Milestone: M8.2 | diterima | |
| ADR-039 | Preserve Domain Ownership Across Shared CapabilitiesKeep Boardflow ordering and movement rules local while reusing bounded mechanics.Milestone: M8.3 | diterima | |
| ADR-040 | Introduce Explicit Product Integration ContractsExchange stable product references without sharing product behavior or persistence.Milestone: M8.4 | diterima | |
| Keragaman framework dan runtime | |||
| ADR-041 | Prefer Framework-Neutral CapabilitiesKeep shared product mechanics independent of React, Next.js, Vue, and Nuxt.Milestone: M9.0 | diterima | |
| ADR-042 | Add a SvelteKit Vertical SliceValidate shared capability boundaries with an independently owned SvelteKit product.Milestone: M9.1 | diterima | |
| ADR-043 | Introduce a Content-Oriented Framework SliceUse Astro for a statically generated knowledge garden while preserving package boundaries.Milestone: M9.2 | diterima | |
| ADR-044 | Introduce Runtime Independence Validation PilihanValidate a Bun-native service while keeping application and package boundaries independent of its runtime.Milestone: M9.3 | diterima | |
| ADR-045 | Introduce Deno Runtime ValidationValidate explicit permissions and Deno-native tooling through an isolated event store.Milestone: M9.4 | diterima | |
| ADR-046 | Introduce Python Service ValidationValidate a separate language ecosystem through an isolated FastAPI inventory service.Milestone: M9.5 | diterima | |
| ADR-047 | Introduce .NET Runtime ValidationValidate the .NET ecosystem through an isolated ASP.NET Core diagnostics service.Milestone: M9.6 | diterima | |
| ADR-048 | Introduce Framework-Neutral Design Tokens PilihanShare visual foundations as immutable data and CSS custom properties without sharing components.Milestone: M10.0 | diterima | |
| ADR-049 | Introduce a Derived Repository Atlas PilihanOrient public visitors through a bilingual presentation consumer whose inventories are derived from repository sources rather than maintained by hand.Milestone: M10.1 | diterima | |