Skip to main content
Koder Stack
Foundations RFCs Specs Policies Registries Compendiums Search
RFCs 146
  • docs/stack/rfcs
  • Agent Console — frontend multi-tenant agnóstico para IAs de CLI/TUI (foundations)
  • Generative UI via KVG (Koder Vector Graphics)
  • Apidocs (AI API Docs Portal): foundations
  • Billing (Usage Tracking): foundations
  • brand-RFC-001 — Brand site architecture
  • Cache (Inference Cache): foundations
  • RFC-001 — Canvas: A2UI (Agent-to-UI) workspace
  • Classify (Classification/NLU): foundations
  • Curator (Autonomous Model Curation): foundations
  • Dataset (Data Pipeline): foundations
  • Koder Design: intentional shape of the Stack (5 facets) + kds.koder.dev landing
  • Extract responsive primitives from per-app implementations into koder_web_kit + koder_kit
  • Koder Design: facets as cross-cutting tags, not single-membership content trees
  • design-RFC-004 — Component preview tooling (Storybook-equivalent)
  • design-RFC-005 — Figma kit + token sync pipeline
  • design-RFC-006 — Cross-language token distribution
  • design-RFC-007 — Token hierarchy (seed / map / alias)
  • design-RFC-008 — Pro opinionated wrappers over primitives
  • design-RFC-009 — Incremental build for design-gen
  • design-RFC-010 — KDS MCP server (hosted streamable-http)
  • design-RFC-011 — kinds-framework refactor for design-gen
  • Verge — Papel de superfície `sunken` (recesso), aditivo à elevação
  • Verge — Registro de superfície `expressive` (entrada/auth espaçosa), aditivo
  • Embed (Embeddings): foundations
  • ERP-RFC-000 — Koder ERP Architecture Overview
  • ERP-RFC-001 — Licitação Vertical Engine
  • ERP-RFC-002 — BPM / Workflow Engine
  • ERP-RFC-003 — Travel and Expense Engine
  • ERP-RFC-004 — Brazilian Fiscal Engine
  • ERP-RFC-005 — Legal Vertical Engine (Lex backend)
  • RFC-001 — Error Reporting Framework
  • Extract (Structured Extraction): foundations
  • RFC-001 — Auth Gate Multi-Channel Notifications
  • RFC-002 — Identity-Aware Proxy: Koder ID SSO at the Koder Jet edge
  • RFC-001 — Delta Delivery
  • RFC-002 — Federation Protocol
  • RFC-003 — Build Attestation for Koder Hub
  • RFC-004 — Upgrade Chains for Koder Hub
  • RFC-005 — Migration Manifests for Upgrade Chain Automation
  • RFC-006 — Hub Unification and Rename (Store → Hub)
  • Hub RFC-007 — apt/deb surface + Termux as first-class consumer
  • id-RFC-015 — Authorization groups & conditional scope grant
  • id-RFC-016 — Kodix as a Koder-ID-joined OS: Koder ID login at the greeter (passkey-first, offline-capable, desktop SSO)
  • id-RFC-017 — Identity-bound full-disk encryption for Kodix: TPM-sealed LUKS, measured-boot + presence-gated unlock (BitLocker+Hello / FileVault parity)
  • Id app RFC 001 stack portal consolidation
  • Imaging: foundations
  • Koder Runtime Strategy — kbox as the universal runtime
  • Self-hosted CI runner pool — move CI off the dev laptop
  • Ephemeral compute lease protocol — TTL + idle-aware transient infra
  • Fleet as a Global, Federated Control Plane
  • Maintenance-Window Control Plane — declarative change windows reconciled by Fleet
  • Backup & Disaster-Recovery Target Architecture — self-hosted-first object store + failure-domain tiering
  • Service Discovery & Edge Routing — runtime endpoint registry in Koder DNS, consumed by Koder Jet; Koder Gate reserved for public product APIs
  • KRDP — Koder Remote Access Protocol + the remote-access product module (RustDesk/AnyDesk/TeamViewer/RDP-class, native & fast, ID-brokered)
  • KDX — Koder Document eXchange (formato universal de documento)
  • Persistent project workspace for Koder Kli (Flow-backed, ephemeral-default)
  • KMD — contrato de página/tema + embed nativo de KVG (fundação do KDX)
  • koder_exec_kit: pluggable execution backends for agent tools
  • RFC-001 — koder_pair_kit: SDK architecture
  • Multi-Tenant Desktop — Koder Kodix Workspaces
  • OS Update Mechanism — koder-os-update
  • OS Rollback & A/B Root — transactional userspace live-update
  • Kompass-RFC-001 — Identity and Organization Unification
  • kompass-RFC-002 — Attachable identifiers & per-org identity policy
  • kover-RFC-001 — Koder Kover: an instrumented comparison cockpit
  • Koder Personal Computer (KPC) — persistent per-user VM for Kode agents 24/7
  • Kruze Companion — a camada Koder do Kruze como extensão multi-browser
  • kruze-RFC-002 — Mosaic tile-tabs + the `koder_tiling` SDK
  • KVG Interact profile — interactive simulation, parametric lighting, walkable 2D→3D scenes
  • Koder Kad — visual KVG project editor: product architecture & shared editing layers
  • KVG — perfil Print + backend KVG→PDF content-stream (export do KDX)
  • kvs-RFC-001 — Worktree-per-session isolation for high-concurrency monorepo work
  • KVS as a concurrent + AI-first forge — the server/host face of Koder Version System
  • KVS-RFC-003 slice d — Virtual always-fresh working copy
  • KVS build-cache KEY contract — content-addressed build-artifact cache over the kvs CAS
  • RFC-001 — MCP Registry: discovery and execution of MCP servers
  • RFC media-dicom-001 — PACS / DICOM Gateway
  • Memory (Agent Long-term Memory): foundations
  • Modelreg (Model Registry): foundations
  • RFC-001 — Area-First Directory Structure
  • RFC-002 — Directory Nomenclature: engine vs. backend at L4
  • RFC-003 — L1 Domain Taxonomy: five domains with a single criterion
  • RFC-004 — L2 Area Definition: thematic grouping within a Domain
  • RFC-005 — L3 Sector Definition: the unit of product/service identity
  • RFC-006 — L4 Distribution Forms: how a Sector reaches the world
  • RFC-007 — L2 Audience-Model Nomenclature: `suite/` becomes `horizontal/`
  • RFC-008 — L5 Language Conventions: idiomatic rules inside each distribution form
  • RFC-009 — Separating Stack Documentation from Agent Configuration in `meta/`
  • RFC-010 — Component Frameworks (Library → Framework Promotion)
  • Multi-DC telemetry ingress: edge-collector tier over the Koder VPN
  • observe-RFC-002 — Koder Push (self-hosted push transport for koder-notify)
  • Playground (Prompt/Agent Playground): foundations
  • Reuse-First policy hierarchy
  • Self-Hosted First policy
  • RFC 003 — Component Policies Hierarchy
  • RFC Phase Pickup (auto-open backlog tickets for pending phases)
  • Prompt (Prompt Registry): foundations
  • RFC-001 — Sandbox: Unified execution sandbox for agents and untrusted code
  • Sandbox (Code Execution): foundations
  • Sandbox: runtime tiers + fleet-scheduled placement
  • Scene3D (3D Generation): foundations
  • RFC-001 — Scheduler: agentic cron for the Koder Stack
  • RFC 001 — Koder Krep (search engine & CLI)
  • Search (Web Search/Scrape): foundations
  • Koder Signer — multi-jurisdiction architecture (BR / EU / US)
  • signs-RFC-001 — Sign-language avatar + bilingual translation across the Koder Stack
  • RFC: Koder Snapshot/Backup — declarative environment capture/restore
  • kdb as unified data plane
  • MCP integration across the Koder Stack
  • Koder Icons — curated shared UI icon library + KDS surface
  • Verge scope expansion — align with Material's 5-layer scope (foundations + styles + components + patterns + accessibility)
  • Full Headless Testability — every Koder UI is automatable/observable/reproducible without a display
  • object storage plane and physical trust tiering
  • credential ownership model and BYO provider keys
  • autonomous model curation, multimodal discovery and benchmark-relevance tracking
  • Internal Service mTLS & East-West PKI — the trust fabric for service-to-service auth
  • GPU streaming platform (Parsec-category) — cloud gaming + remote GPU workstation
  • Shadow / Parallel-Run Validation — validate risky backend changes in prod without blocking windows
  • UI Interaction Performance Corpus — comparative request→painted latency tiers for reusable interaction primitives
  • Spec-driven Requirement/Scenario grammar + spec-delta lifecycle — internalise OpenSpec's best ideas into the Koder Stack's own spec infra
  • Spec-adherence harness — trigger registry as SSOT, just-in-time spec injection, and gates with a false-positive budget
  • Kanon — the named, versioned, non-Turing-complete rule-expression language + the declarative evaluator that replaces hardcoded Go checkers
  • stack-RFC-016 — Koder Governance Plane (norte)
  • Self-Hosted Source Catalog & Radar — generalize the mirror+refresh+discover+rank pipeline for any imported content, and surface ranked self-hostable options to Stack admins
  • Clean URLs for static Koder sites — locale negotiation + extensionless, no trailing slash
  • koder twillio cpaas — control-plane over a shared transport substrate
  • stack-RFC-019 — Koder UI render strategy: Verge over wgpu/Vello
  • stack-RFC-020 — AI compute strategy: rent the kernels, own the layers, shadow the vendor-neutral runtime
  • stack-RFC-020 — Operator Plane, Apex Root e o Kode Agent Service
  • stack-RFC-021 — Kroma ↔ Koder compositor (kompose) & DE (Kolide) contract
  • stack-RFC-021 — Stack Graph: grafo de conexões gerado, glossário e JIT component-aware
  • stack-RFC-022 — Kroma Web Backend: the declarative UI on a browser canvas (WebGPU)
  • stack-RFC-023 — Kroma Web Module Packaging & Shared Runtime
  • stack-RFC-024 — Superfícies de conhecimento: naming e portais (Atlas geo · Compêndios · Stack Explorer)
  • stack-RFC-025 — Seleção de dispositivo GPU e política de energia (contrato compartilhado, backends por-engine)
  • Synth (Audio Synthesis): foundations
  • TAKE-RFC-001 — Koder Take Architecture Overview
  • Tools (Tool Registry): foundations
  • Trace (AI Tracing/Observability): foundations
  • Training (Fine-tuning Service): foundations
  • Translate (Translation): foundations
  • Tribus (cooperative-work primitive): foundations
  • Video: foundations
  • Vision: foundations
  • Workflow (Agent DAG/State Machine): foundations
Home / RFCs / RFC-010 — Component Frameworks (Library → Framework Promotion)

RFC-010 — Component Frameworks (Library → Framework Promotion)

Field Value
Status Draft (2026-05-02)
Author(s) Rodrigo (with Claude as scribe)
Date 2026-05-02
Affects `engines/sdk

Source: meta/docs/stack/rfcs/monorepo-RFC-010-component-frameworks.md · Edit this page

Last updated 2026-06-28 · commit 638a56216

← RFC-009 — Separating Stack Documentation from Agent Configuration in `meta/` Multi-DC telemetry ingress: edge-collector tier over the Koder VPN →
Koder Stack

The public documentation portal of the Koder Stack — RFCs, specifications, policies, registries and compendiums, rendered from the monorepo.

Documentation

Foundations RFCs Specs Policies Registries

Browse

Modules Runbooks Compendiums Search

Koder

koder.dev Flow Hub Brand

© 2026 Koder · Generated by koder-docs-render v0.5.0