Change a data-* and watch the field answer. Edit the attributes on the actual DOM body. The host authors force and strength; the field computes a reading; CSS projects feedback onto that same element. data-body="attract" Authoredattract · strength 0.9 Measuredlocal field density 0.00 ProjectedThe same DOM body changes emphasis through its --d feedback signal. A real interface you’d actually build. These questions are ordinary DOM elements. Their authored urgency sets relative influence; the field measures local activity and writes a signal back to the page. Focus or point at a question to see the hierarchy respond. Keep meaning in data. Let the field measure interaction. A page can author importance, declared relationships, and interaction state as inputs. The field measures how those inputs combine over time; the host chooses how to present each signal and when to recompute product data. See conserved attention → Stop building the systems that exist because the DOM is blind. The DOM stores structure and meaning, while application code often computes rankings, relations, and freshness separately. Fundamental offers a shared runtime for declared inputs and measured signals; the application still owns its data, rules, and consequential decisions. Priority you don’t re-sort. You still author importance (a data-strength); how it plays out is a live field reading (--d, with --field-density as the field-namespaced alias), not a list you re-sort and re-render on every change. See it work → “Everything is P1,” solved by a law. Attention is one conserved budget — emphasize one thing and the rest necessarily yield. The normalization pass teams enforce with scoring schemes and meetings becomes something the runtime cannot violate. See it work → Declared relationships can shape influence. The host supplies edges; a selected pattern determines how they affect the field. The app still owns the relationship data. See it work → Freshness needs an authored time signal. A decay force can continuously interpret age or recency supplied by the host; it does not replace persistence or scheduled work. See it work → One measured field, several projections. CSS feedback, DOM state, and query output can read the same simulation; each host decides when to project or update its own view. See it work → Fundamental doesn’t hand you a better abstraction over these jobs. It makes the question each one answered — what matters, what’s related, what’s stale — answerable by the field — so the re-sort, the timer and the hand-kept graph go away. Your data and your rules stay yours. Declare, influence, read, reveal, govern. Five verbs are the whole loop. You declare host objects into the field; forces influence them through declared channels; you read the state back; projections reveal it; policy governs what may run and what an agent may read. DeclareHost objects become bodies — a data-body attribute, addBody(), or a declared edge. InfluenceForces act through declared channels, accumulated centrally — deterministic and replayable. Readquery() and snapshot() expose the field as plain, serializable state. RevealProjections express that state through CSS variables, DOM attributes, JSON, native views, or overlays. GovernPolicies, budgets, redactions, lane lints, and reduced-motion rules constrain what runs and what an agent reads. Want the exact API? Read the docs. Want the live engine? Open the manual. Want the substrate proof? One field, two readings → Built to be inspected. Zero runtime dependencies. The core engine ships with none. Signals-first by default. A field renders nothing unless you ask for it — the invisible field is the baseline, so no component has to become a canvas. Accessibility isn’t a mode. The field is a measurement, so reduced motion freezes the picture and the signal stays — the same --field-* value, held still. Semantic HTML stays the source of meaning; enforced, linted, verified per surface. Measured, not guessed. Frame and fill-rate budgets are measured on real hardware; see the performance methodology. Stable 0.x surface, cross-plane conformance. Code-verified docs, a public surface guarded against silent removal by check:api, and shared-physics conformance across web, Apple, and Android. Try the field Follow the particles to the data console. When enabled, this DOM button declares a morph target sampled from the inline SVG path. The particles form a short arrow above the fixed console control. With reduced motion, particle travel stays off; the explanation and console remain available. The fixed console button opens performance and platform diagnostics. It answers how this page is running. This query reports field state, including bodies, forces, and simulation metrics. It answers what the field currently contains. reading the field… 37 forces. 64 patterns. 9 presets. One 0.x API. Everything above is built from one contract: data-* in, --field-* out. The complete force-by-force manual — every force, preset, and system behaviour, each demo running live on the real engine — now has its own page, so the homepage can stay about the substrate. Or jump straight to a surface: the API · patterns · the force catalog. Built on this, running now. Four ways in: the web packages, the native Swift and Kotlin ports, and Three.js — one physics, held to a shared conformance test. One engine, many hosts. The core computes field behavior from host-supplied state and imports zero DOM. Adapters connect it to web, native, custom-renderer, and headless surfaces; supported capabilities differ by host: Web — @fundamental-engine/dom binds the engine to the page: every [data-body] element a body, feedback returned as --field-* variables. The primary surface — and what this page runs on. Native — a Swift port runs the same field on Apple platforms (Metal / SwiftUI), and a Kotlin port runs it on Android (Jetpack Compose, plus a non-Compose View/Canvas host). See Implementations for host capabilities and conformance details. Your renderer — @fundamental-engine/three drives a THREE.Points swarm in your own WebGL scene; the read primitives (sample, readParticles, addField) bind the engine to anything that draws. Headless — no DOM, no canvas: records become bodies and relationships become edges, and a tool reads the field through query() and snapshot(). The smallest conformant host — for servers, tests, and agents. How the hosts relate — and what’s at parity across them — in Implementations. Make model output you can read at a glance. A host can declare claims, sources, confidence, and support relationships as data. The field measures their declared arrangement; the host decides what confidence means and which actions are allowed. Inspect the source links, then compare the visual projection with the serializable query. The same deterministic math drives the Evidence and Search studies. Host-supplied: confidence, source identity, and declared support. Engine-measured: arrangement and density. The geometry does not validate a claim. Everything above shows the field. These twelve never do. Twelve ordinary page types — an inbox, a market, a backlog, a front page — run as fields over real data: no particle swarm, the measurements come back as type, ink, and anchor. Each ships its data as a committed snapshot, upgrades itself to live counts when the source is reachable, and says which mode it's in. See the family → Add it to the stack you already have. One package per framework — pick the one for your stack and you’re done. Each bundles the engine (core + the DOM binding) for you; there’s nothing to wire together. Own the canvas / building your own renderer? @fundamental-engine/core is the renderer-agnostic engine — you supply a host (Core guide). You don’t install @fundamental-engine/dom directly — the packages above already bundle it for you. No build step? Import from a CDN (playground / prototyping only): import { createField }from 'https://esm.sh/@fundamental-engine/vanilla' The full package map and an install-to-reacting-headline walkthrough live in the docs. Go deeper.
AI NEWS JOURNAL
Hacker News Show HNAI NEWS / JOURNAL
Show HN: Fundamental, page elements that bend a shared field and read it back
Article URL: https://fundamentalengine.com/ Comments URL: https://news.ycombinator.com/item?id=50592369 Points: 1 # Comments: 0
翻译服务暂未运行,当前显示原文。