axiom-appkit 0.0.1__tar.gz

axiom_appkit-0.0.1/.github/workflows/ci.yml

@@ -0,0 +1,20 @@
+name: ci
+on: { push: { branches: [main] }, pull_request: {} }
+jobs:
+  python:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with: { python-version: "3.11" }
+      - run: pip install -e ".[dev]"
+      - run: ruff check src
+      - run: pip install fastapi httpx && pytest -q
+  frontend:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with: { node-version: "20" }
+      - working-directory: frontend
+        run: npm install && npm run typecheck

axiom_appkit-0.0.1/.github/workflows/publish.yml

@@ -0,0 +1,67 @@
+# Copyright (c) 2026 B-Tree Labs
+# SPDX-License-Identifier: Apache-2.0
+#
+# Publish axiom-appkit to PyPI — the same mechanism as axiom-os-lm: a trusted
+# publisher (OIDC), no stored token, triggered on v* tags. The source repo stays
+# private; the wheel is public on PyPI, so any Axiom node installs appkit as an
+# ordinary dependency (no deploy key, no credential).
+#
+# ONE-TIME SETUP (owner action, mirrors axiom-os-lm): on pypi.org, create/claim
+# the `axiom-appkit` project and add a GitHub trusted publisher —
+#   owner: b-tree-labs · repo: axiom-appkit · workflow: publish.yml · environment: pypi
+# Until that exists the publish step fails with `invalid-publisher` (this is the
+# axiom v0.7.0–v0.10.1 lesson: configure the publisher before the first tag).
+
+name: Publish to PyPI
+on:
+  push:
+    tags: ["v*"]
+  workflow_dispatch:
+    inputs:
+      ref: { description: "Tag or commit to publish", required: true, default: "main" }
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with: { python-version: "3.11" }
+      - run: pip install build
+      - run: python -m build
+      - uses: actions/upload-artifact@v4
+        with: { name: dist, path: dist/ }
+
+  publish:
+    needs: build
+    runs-on: ubuntu-latest
+    permissions: { id-token: write }
+    environment: pypi
+    outputs: { version: "${{ steps.v.outputs.version }}" }
+    steps:
+      - uses: actions/download-artifact@v4
+        with: { name: dist, path: dist/ }
+      - id: v
+        run: |
+          wheel=$(ls dist/*.whl | head -1)
+          version=$(basename "$wheel" | sed -E 's/^axiom_appkit-([^-]+)-.*/\1/')
+          echo "version=$version" >> "$GITHUB_OUTPUT"
+          echo "Publishing axiom-appkit $version"
+      - uses: pypa/gh-action-pypi-publish@release/v1
+
+  post_publish_smoke:
+    needs: publish
+    runs-on: ubuntu-latest
+    steps:
+      - name: Wait for PyPI to index, then install + import
+        env: { VERSION: "${{ needs.publish.outputs.version }}" }
+        run: |
+          set -euo pipefail
+          pip install --upgrade pip
+          for a in $(seq 1 30); do
+            if pip index versions axiom-appkit 2>/dev/null | grep -q "$VERSION"; then
+              echo "axiom-appkit $VERSION resolvable"; break
+            fi; sleep 10
+          done
+          pip install "axiom-appkit==$VERSION"
+          python -c "import axiom_appkit; assert axiom_appkit.design_tokens_css().find('--accent')>=0; print('import + tokens ok')"

axiom_appkit-0.0.1/.gitignore

@@ -0,0 +1,11 @@
+__pycache__/
+*.pyc
+.venv/
+dist/
+build/
+*.egg-info/
+node_modules/
+frontend/dist/
+.coverage
+.pytest_cache/
+.ruff_cache/

axiom_appkit-0.0.1/CHANGELOG.md

@@ -0,0 +1,15 @@
+# Changelog
+
+All notable changes to axiom-appkit are documented here. Format follows
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/); versioning follows SemVer.
+
+## [Unreleased]
+
+### Added
+
+- Repository scaffold: Python package (`axiom_appkit`) with the Axiom composition
+  hook and extension manifest; React + Vite + TypeScript + Tailwind frontend skeleton.
+- **Design tokens** — the single source of truth for the Axiom app design system
+  (IBM Plex pairing, the light/dark token palette, burnt-orange accent), extracted
+  from the hand-repeated CSS in the consumer surfaces.
+- **AppShell** — the shared top-bar / brand / identity / nav shell component.

axiom_appkit-0.0.1/LICENSE

@@ -0,0 +1,17 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   Copyright (c) 2026 B-Tree Labs
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

axiom_appkit-0.0.1/NOTICE

@@ -0,0 +1,6 @@
+axiom-appkit
+Copyright (c) 2026 B-Tree Labs
+
+The domain-agnostic front-end and application framework for Axiom (AEOS).
+Composes into a single Axiom node; consumed by independent tenants (e.g.
+NeutronOS and SoilMetrix). No consumer-domain content belongs in this repo.

axiom_appkit-0.0.1/PKG-INFO

@@ -0,0 +1,57 @@
+Metadata-Version: 2.5
+Name: axiom-appkit
+Version: 0.0.1
+Summary: Domain-agnostic front-end and application framework for Axiom (AEOS)
+Project-URL: Homepage, https://github.com/b-tree-labs/axiom-appkit
+Project-URL: Repository, https://github.com/b-tree-labs/axiom-appkit
+Author: B-Tree Labs
+License: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Keywords: aeos,axiom,fastapi,framework,frontend
+Requires-Python: >=3.11
+Provides-Extra: axiom
+Requires-Dist: axiom-os-lm>=0.10; extra == 'axiom'
+Provides-Extra: dev
+Requires-Dist: pytest>=8; extra == 'dev'
+Requires-Dist: ruff>=0.6; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# axiom-appkit
+
+The domain-agnostic **front-end and application framework** for Axiom (AEOS) — the
+tier above Axiom's HTTP primitives (`http`, `webgate`, the mount registry) that turns
+declared surfaces into one coherent application: a shared design system, a React + Vite
++ TypeScript app shell and component library, FastAPI application conventions, and the
+agent-management and prompt-engineering surfaces.
+
+## Position
+
+```
+React app shell + component library     (this repo, frontend/)
+        │
+FastAPI app conventions + mounts        (this repo, src/axiom_appkit/)
+        │  composes via the extension registry into
+Axiom node — http / webgate / registry  (axiom core)
+        │
+axiom.infra.db  (ORM + OLTP)  ←  routine upsert from the medallion gold layer
+```
+
+- **Standalone, but it composes.** appkit is its own package with its own release
+  cadence; it registers into the *one* Axiom node via the extension manifest, never a
+  separate runtime.
+- **Domain-agnostic by construction.** No reactor, no agriculture — appkit is proven by
+  two independent tenants and carries neither's domain. Consumers supply their brand,
+  their surfaces, and their data.
+- **Extend, don't fork.** Persistence rides `axiom.infra.db`; HTTP rides Axiom's mount
+  registry. appkit is the application tier on top.
+
+## Layout
+
+| Path | What |
+|---|---|
+| `frontend/` | React 18 + Vite + TypeScript + Tailwind — design tokens, app shell, components |
+| `src/axiom_appkit/` | FastAPI app conventions + the composition hook that mounts appkit into an Axiom node |
+| `src/axiom_appkit/extensions/builtins/appkit/` | the `axiom-extension.toml` manifest for discovery |
+
+Apache-2.0. Copyright (c) 2026 B-Tree Labs.

axiom_appkit-0.0.1/README.md

@@ -0,0 +1,38 @@
+# axiom-appkit
+
+The domain-agnostic **front-end and application framework** for Axiom (AEOS) — the
+tier above Axiom's HTTP primitives (`http`, `webgate`, the mount registry) that turns
+declared surfaces into one coherent application: a shared design system, a React + Vite
++ TypeScript app shell and component library, FastAPI application conventions, and the
+agent-management and prompt-engineering surfaces.
+
+## Position
+
+```
+React app shell + component library     (this repo, frontend/)
+        │
+FastAPI app conventions + mounts        (this repo, src/axiom_appkit/)
+        │  composes via the extension registry into
+Axiom node — http / webgate / registry  (axiom core)
+        │
+axiom.infra.db  (ORM + OLTP)  ←  routine upsert from the medallion gold layer
+```
+
+- **Standalone, but it composes.** appkit is its own package with its own release
+  cadence; it registers into the *one* Axiom node via the extension manifest, never a
+  separate runtime.
+- **Domain-agnostic by construction.** No reactor, no agriculture — appkit is proven by
+  two independent tenants and carries neither's domain. Consumers supply their brand,
+  their surfaces, and their data.
+- **Extend, don't fork.** Persistence rides `axiom.infra.db`; HTTP rides Axiom's mount
+  registry. appkit is the application tier on top.
+
+## Layout
+
+| Path | What |
+|---|---|
+| `frontend/` | React 18 + Vite + TypeScript + Tailwind — design tokens, app shell, components |
+| `src/axiom_appkit/` | FastAPI app conventions + the composition hook that mounts appkit into an Axiom node |
+| `src/axiom_appkit/extensions/builtins/appkit/` | the `axiom-extension.toml` manifest for discovery |
+
+Apache-2.0. Copyright (c) 2026 B-Tree Labs.

axiom_appkit-0.0.1/docs/soilmetrix-appkit-migration.md

@@ -0,0 +1,96 @@
+# SoilMetrix → axiom-appkit migration ledger
+
+**Status:** living document · **Owner:** Ben Booth · **Audience:** appkit + SoilMetrix + NeutronOS devs
+
+## The plan
+
+Extract everything in SoilMetrix that is **not agriculture-specific** into `axiom-appkit`,
+feature by feature. For each extracted feature the sequence is the same:
+
+1. **Extract** the generic capability into appkit (domain-agnostic, no soil, no reactor).
+2. **Adopt in SoilMetrix** — SoilMetrix swaps its bespoke implementation for the appkit
+   version (back-compatible by construction — appkit must not force a rewrite).
+3. **Deploy as foundation in NeutronOS** — the same appkit version becomes the basis of the
+   NOS front end.
+
+Two independent tenants (SoilMetrix = agriculture, NeutronOS = nuclear) prove each feature is
+genuinely domain-agnostic. Where appkit can do better than SoilMetrix's current version
+(agent management, prompt engineering, auth), the extraction is also an **upgrade**.
+
+**The rule:** a feature is agriculture-specific if it references crops, soil, fields, zones,
+SSURGO/Modus/geospatial-soil, or the patented ML soil pipeline. Everything else is a candidate.
+
+## Ledger
+
+Legend — appkit: ☐ not started · ◐ in progress · ☑ shipped. SoilMetrix / NOS: ☐ · ◐ · ☑ adopted.
+
+| # | SoilMetrix feature | Agriculture-specific? | appkit target | appkit | SoilMetrix swap | NOS adopt |
+|---|---|---|---|---|---|---|
+| 1 | Design system / CSS tokens | No | `tokens.css` (single source) | ◐ | ☐ | ☐ |
+| 2 | App shell (top bar / brand / identity / nav) | No | `AppShell` | ◐ | ☐ | ☐ |
+| 3 | FastAPI app conventions (routes/services/models/middleware/validation) | No | appkit FastAPI scaffold | ☐ | ☐ | ☐ |
+| 4 | ORM base + OLTP session | No | extend `axiom.infra.db` | ☐ | ☐ | ☐ |
+| 5 | gold → OLTP upsert primitive (`ON CONFLICT UPDATE`) | No | appkit upsert primitive | ☐ | ☐ | ☐ |
+| 6 | Auth | No — **DEEP MERGE** (see below) | webgate base + SoilMetrix depth | ◐ | ☐ | ☑ (NOS gate) |
+| 7 | Forms + typed validation (React Hook Form + Zod) | No | appkit forms | ☐ | ☐ | ☐ |
+| 8 | Chart / viz components | No | appkit chart components (Signal Studio-derived) | ☐ | ☐ | ☐ |
+| 8a | App shell (top bar / nav) | No | `AppShell` | ◐ | ☐ | ☐ |
+| 8b | Three-region layout (left rail / center / right dock, collapsible + resizable + persisted) | No | `WorkbenchLayout` + `usePanel` | ◐ | ☐ | ☐ |
+| 8c | Chat UX idiom (log + composer + suggestions, dockable) | No | `ChatDock` | ◐ | ☐ | ☐ |
+| 9 | AI chat / agent infra | No — **DEEP MERGE** (see below) | unified agentic chat | ☐ | ☐ | ☐ |
+| 10 | Prompt infra | No — **DEEP MERGE** (see below) | versioned + evaluated prompt system | ☐ | ☐ | ☐ |
+| 11 | RAG / chat surface | No (corpus is tenant's) | appkit chat surface + tenant RAG | ☐ | ☐ | ☐ |
+| 12 | Admin / ops MCP surface | No | appkit admin surface | ☐ | ☐ | ☐ |
+| 13 | Observability / metrics / health conventions | No | appkit app conventions | ☐ | ☐ | ☐ |
+| 14 | Map / field viewer (Leaflet/MapBox, field geometry) | **YES — stays in SoilMetrix** | — | — | — | — |
+| 15 | Soil ML pipeline (SSURGO, Modus, ensemble models) | **YES — stays in SoilMetrix** | — | — | — | — |
+| 16 | Crop / yield / zone-map domain models | **YES — stays in SoilMetrix** | — | — | — | — |
+
+## Deep merges — prove, don't regress (chat, prompt, auth)
+
+Three items are **not extractions** — they are **merges of two mature systems**, and the risk is
+entirely regression of depth that already works. They get a different, slower discipline than the
+FE extractions. Do not swap either side out until the unified capability is proven a strict
+superset of both.
+
+**The discipline for each deep merge:**
+
+1. **Inventory both sides honestly.** Write down what each system already does well — the features
+   a user would notice if they disappeared. Neither side is assumed to be the base.
+2. **Design the union as a strict superset.** The appkit version must do everything both sides do,
+   or the gap is named and accepted explicitly. "Better" is a claim to be proven, not assumed.
+3. **Prove no regression against BOTH tenants.** A parity harness / evaluation — real conversations,
+   real prompts, real logins — comparing the unified capability against each original, before any
+   cutover. Vibes do not count; this is the same posture as validating a ROM against measurement.
+4. **Cut over behind a flag, with rollback.** Each tenant flips when its parity passes, not on a
+   shared date. Keep both paths runnable until the flag has burned in.
+5. **Retire the originals only after burn-in.** The two systems coexist until the unified one has
+   carried real traffic without regression.
+
+| Deep merge | SoilMetrix depth (don't lose) | NOS / Axiom depth (don't lose) | Unified target |
+|---|---|---|---|
+| **AI chat infra** | Field Hand agentic chat: tool actions, clarification, UI commands, artifacts, web-search sources, voice replies, custom instructions, multi-account, chat library/rename/move | Tenant-scoped ask grounded in gold verbs + the site corpus; the fused-RAG engine (semantic + structured tool-calling); `neut chat`; chat memory | One agentic chat: appkit owns the surface + orchestration; retrieval and tools stay tenant-scoped; both tenants' feature sets present |
+| **Prompt infra** | Custom instructions, per-context prompt assembly | Prompts as versioned, evaluated platform assets; per-site / per-surface assembly by construction | One prompt system: versioned + evaluated assets, per-tenant/per-surface assembly, custom instructions preserved |
+| **Auth** | Account model, staff tiers, OpsGate/TermsGate, reverify, session UX | webgate: OIDC/Entra SSO, ES256 sessions, forward-auth, roles, audit — **ahead on SSO/MFA/audit** | webgate as the base (the upgrade direction), but only after SoilMetrix's account/staff-tier/terms/reverify depth is carried — an adopt, not a naive swap |
+
+These land **after** the low-risk FE extractions. The chat *UI* shell (`ChatDock`) is safe and
+already extracted; the chat *engine/infra*, the prompt infra, and auth are the deep merges that
+wait for the parity discipline above.
+
+## Notes per feature (filled in as we work each one)
+
+- **#1 Design tokens (in progress):** appkit ships `tokens.css` as the single source; the
+  palette structure is appkit's, brand values (`--accent`) are tenant overrides (NOS burnt
+  orange, SoilMetrix green). NOS surfaces (`home.py`, studio `PAGE_TEMPLATE`) currently inline
+  these tokens; swap them to link `/_appkit/tokens.css`.
+- **#2 AppShell (in progress):** the top bar (brand, context name, identity, nav) both tenants
+  repeat. appkit `AppShell` is the shared component; consumers pass brand + nav + user.
+- **#8b WorkbenchLayout (in progress):** generalized from SoilMetrix's `ForeFlightLayout` — the
+  three-region frame (left nav rail, center that keeps min width, right dock) with per-key width
+  persistence, drag-to-resize with snap-to-collapse, and responsive collapse to overlays on narrow
+  viewports. `usePanel` is the shared collapsible/resizable/persisted primitive both sides use.
+  Maps 1:1 onto Signal Studio's rail/chart/chat, so NOS is the immediate first consumer.
+- **#8c ChatDock (in progress):** the right-panel chat idiom from Field Hand, stripped to the shape
+  — scrolling message log, pinned composer, starter suggestions, header actions slot — with content
+  and the send handler supplied by the consumer. No agriculture, no reactor.
+- Later rows get their own note + a spec section here when we pick them up.