Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
59 changes: 58 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,9 @@ The desktop application is named **Rangoon**; Rangoon.si is the product wordmark

**Current status:** an experimental native workbench with persistence, immutable skill/workflow revisions, composition, compilation/export/inspection and explicitly consented advisory model paths. The ordinary desktop source enables encrypted-workspace startup by default, with explicit setup/unlock and no plaintext fallback. Encrypted recovery has dated disposable macOS evidence, including recovery into a fresh independently keyed workspace and restart. Windows startup/custody/recovery remains unsupported in the current implementation; Linux GUI/custody and packaged release qualification remain open. Original instruction files and deliberately readable exports are outside workspace encryption. No live agent executor, scheduler, authority adapter or plugin runtime is mounted.

The [October 29 whole-application audit](docs/system-audit.md#october-29-whole-application-viability-and-drift-audit) reconciles current source against earlier architecture and usability checkpoints. The [completion plan](docs/plan.md#october-15-audit-completion-sequence) puts recovery, installed local tasks and usable editing ahead of more disconnected demonstrations. The [development ledger](docs/development.md) records exact validation and limits. Source tests, checksums, model reviews and source CI do not establish runtime enforcement, target-loader compatibility, desktop support or certification.
The [October 29 whole-application audit](docs/system-audit.md#october-29-whole-application-viability-and-drift-audit) reconciles current source against earlier architecture and usability checkpoints. The [completion plan](docs/plan.md#next-phase-packets--november-1-2026) puts recovery, installed local tasks and usable editing ahead of more disconnected demonstrations. The [development ledger](docs/development.md) records exact validation and limits. Source tests, checksums, model reviews and source CI do not establish runtime enforcement, target-loader compatibility, desktop support or certification.

**Workbench update — November 3:** continue exact saved revisions from Skills or Compose into Compile while preserving dirty drafts and historical pins. Task-oriented controls, 57 original full-color icons, packaged software marks and Recipe/Graph output navigation make the local workflow clearer; long titles and sixteen-output/recovery cases are covered by source and synthetic UI tests. Current source checks pass 670 JavaScript tests; headless software-rendered browser review completes 110 layout profiles and 30 checks while retaining native-select/Lock-pointer gaps. Opt-in memory-only replay also covers saved-result routing, exact revision/focus and dirty/busy/late-result guards; it is not native persistence evidence. Disposable native folder fixtures now bind their exact identity and require newly created manifest-v3 runs; this does not qualify the installed encrypted workflow. See the [publication scope and evidence](docs/development.md#november-3-reviewed-workbench-publication).

**Review today:** [the reviewer guide](docs/reviewer-guide.md) provides a short design/source task and a disposable-data native task. Browser samples and playgrounds are synthetic. The local Operations window reads one selected report and shows unverified observations; it is not a live feed. Use disposable data in an explicitly isolated review profile. Earlier macOS recovery evidence does not qualify the current working tree, normal-profile migration or every platform. Broader desktop beta and three-OS release support have separate qualification gates.

Expand All @@ -25,6 +27,57 @@ Approval management, redacted correlated telemetry and live operations visualiza

The [cross-runtime operator-record target](docs/operations-control-plane.md#cross-runtime-operator-record-acceptance-target) defines what Rangoon must show for denied, approved, changed, repeated and uncertain actions. It prioritizes read-only OpenShell observations for this goal while LNSAT evidence remains an independent later gate. No live cross-runtime record exists today.

## Compile setup refinement — November 2, 2026

Output format and Compile actions now appear above long saved-skill/history lists, with selected-revision context and nearby stale-selection recovery. Existing action gates and export warnings remain. Local source checks pass 660 tests; eight bounded ARM-browser layout captures completed with clean teardown; complete interaction and native workflow qualification remain open. [Evidence](docs/development.md#ui-c5-compile-control-placement--november-2-2026).

## Full-color icons and software identities — November 2, 2026

The workbench now uses 57 original filled, multi-color object icons, with the original monochrome shapes retained for high-contrast mode. Software identities include locally packaged authentic marks for agentgateway, Cerbos, Permit and Invariant, alongside Claude, Rangoon, LNSAT and VUSL. Existing availability, authorization and action gates are unchanged. View the [color gallery](preview/icon-gallery.html) and [asset provenance](preview/assets/vendors/provenance.json).

JavaScript checks pass 659 tests and independent rendered visual review passes. Browser runs captured all 44 viewport/theme profiles but failed during repeated Lock input; complete interaction and native-workflow qualification remain open. See the [full-color receipt](docs/development.md#ui-c4-full-color-artwork-and-software-marks--november-2-2026).

## Visual organization and icons — November 2, 2026

The workbench now uses a 57-symbol local icon system for actions, records, storage states and systems. Skills, Compile, Lock and backup/export controls retain their text and behavior. Real packaged software marks identify Claude, Rangoon, LNSAT and VUSL; other software uses generic category symbols beside its name. The [icon gallery](preview/icon-gallery.html) separates identity from connection or support claims. Desktop navigation scrolls while Lock/theme stay reachable, and disabled primary actions use neutral styling.

JavaScript checks pass 652 tests. Synthetic browser validation completed 44 viewport/theme profiles and 17 checks; qualification remains partial for actual native dropdown input. Current native encrypted workflows and real-user usability require separate proof. See the [inspection and validation receipt](docs/development.md#ui-i3-semantic-icons-and-visual-organization--november-2-2026).

## Task-focused editing — November 2, 2026

Skills now groups tools by task: find or create in the library, edit a revision, continue with its saved version in Compose/Compile, and inspect origin/history. Search stays visible; optional filters retain their state and show active facets. Recovery explanations sit beside relevant controls, and conflict reload appears above the editor.

Source checks pass 648 tests. Synthetic browser checks completed 14 viewport/theme profiles and 17 interaction/media/controller cases; overall qualification remains partial because native dropdown input is unverified. Native encrypted persistence and the latest desktop artifact still require separate qualification. See the [task-arrangement receipt](docs/development.md#ui-t2-task-arrangement-and-interaction-audit--november-2-2026).

## Workbench refinement — November 1, 2026

Skills keeps revision actions above the editor, with more compact task headers, clearer title typography, responsive content sizing and consistent dark/light surfaces. Existing draft, conflict, history and exact-revision rules stay intact. The native development executable has been rebuilt offline with these frontend changes.

Isolated synthetic browser checks now cover 14 viewport/theme profiles, including emulated 4K/DPR layouts, and 11 pointer/keyboard/recovery states. All desktop revision actions stayed above the fold and all tested action targets met 44×44 pixels. This is browser/source evidence, not a packaged release or qualified native encrypted workflow. See the [rendered/build receipt](docs/development.md#ui-r1-rendered-workbench-refinement-and-native-rebuild--november-1-2026).

## Source update — November 1, 2026

Skills and Compose now preserve exact saved revisions in both directions: add a saved skill to Compose, then inspect an actual saved output in Skills without silently substituting a newer revision. Native readback precedes result navigation; unsaved edits, busy states, duplicate/full inputs and open drafts retain work and explain recovery. Navigation and Lock reject stale replies. Draft creation, preview, save, review, compilation and export remain explicit.

The disposable native harness also binds a synthetic folder and exact file inventory to each test run, rejecting mutation/replacement/link/unexpected-child cases before and after phases. The roadmap reconciles local completion with later authenticated peers, credential/key lifecycle and enterprise operation boundaries. Live peers, cloud control and distributed dispatch remain planned.

These are source changes, not a desktop release. Current rendered/native encrypted-workflow qualification remains open; Windows/Proxmox testing is deferred and Windows custody/startup/recovery still needs implementation. Source tests do not qualify normal user data, provider enforcement or compliance. The [publication receipt](docs/development.md#source-branch-publication--november-1-2026) records the exact scope and evidence.

## Build direction and next phases — November 1, 2026

Rangoon keeps its local-first capability workbench and native Rust trust boundary while improving project/target task continuity. The [prepared packet sequence](docs/plan.md#next-phase-packets--november-1-2026) starts with an artifact-bound encrypted local journey, then exact-revision editing/composition, retained file inspection, reversible instruction-file changes, one verified target-loading handoff and practical bulk organization. Original bytes and revisions stay authoritative; future syntax projections/indexes are derived and versioned.

Finished radials, bars, icons, packaged system logos and refined abstract Rangoon artwork remain part of the [visual contract](docs/visual-system.md). Metrics must show real scope/counts/freshness and inspectable detail, with complete empty, stale, partial, denied, failure and recovery states. These docs do not claim that the proposed UI or enterprise features are implemented.

Later [peer/enterprise work](docs/application-architecture.md#enterprise-operation-and-custody-boundaries--november-1-2026) requires verified tenant/actor scope, target-side operation guarantees, current ownership, scoped credentials/key lifecycle and recovery before writes or failover. Cloud hosting, cloud resource management and model inference are distinct profiles. Shared services, KMS/BYOK/federation, live peers and distributed dispatch remain planned; optional engines and VUSL retain their independent boundaries. Local usefulness does not wait for enterprise infrastructure. The [development receipt](docs/development.md#direction-reconciliation--november-1-2026) records this documentation-only reconciliation and remaining gates.

## Local qualification preparation — October 30, 2026

The disposable macOS harness now includes the existing folder-metadata and explicit file-inspection permissions, plus a fixed synthetic folder bound to the run manifest and artifact inventory. It rejects changed contents, replaced entries, links and unexpected children before and after a phase. Input-integrity results remain separate from native UI results; the [manual workflow checklist](docs/reviewer-guide.md#disposable-native-workflow-checklist) still needs a fresh artifact and actual picker, Lock, restart and recovery observations. See the [development receipt](docs/development.md#nq-1-disposable-folder-qualification-preparation--october-30-2026) for validation and limits.

Windows testing is deferred until the new Proxmox test host is available. Windows encrypted custody/startup/recovery implementation and three-OS GUI qualification remain outstanding. The next local milestones are a repeatable encrypted workflow, retained folder-row inspection, reversible project-file changes and one verified target-loading handoff.


## Application source update — October 29, 2026

This update brings the current local workbench into one source snapshot: encrypted default startup and recovery, instruction-history persistence, native lifecycle hardening, bounded Agent files and folder metadata, Markdown review/find, and exact saved-skill handoff to Compile. It preserves the newer public LNSAT offline inspection modules and independent VUSL direction. Rust manifests, local checks and source CI use the same **1.99.1** toolchain. Windows validation resolves the logical Cargo tool through rustup, then uses the returned absolute `.exe` paths; it never falls back to an unrelated compiler on PATH. The default encrypted Windows source build requires OpenSSL headers and the x64 MSVC import library; CI validates the hosted runner’s preinstalled copies explicitly. This build configuration does not enable the still-unsupported Windows workspace startup or key custody. Recovery-journal ownership now explicitly releases its lock at teardown, including when a duplicate handle survives temporarily; active competing owners still refuse access.
Expand All @@ -35,6 +88,10 @@ Folder browsing returns metadata; inspecting content still requires an explicit

**Open in Compile** carries a selected saved skill revision directly from Skills into Compile through an exact native read. Historical selection stays pinned; compilation, format choice and export remain explicit. Dirty edits for that skill, conflicts and pending requests block the handoff with recovery guidance. Navigation and Lock invalidate late reads. This slice has source-test evidence; the full-publication receipt records its additional synthetic rendered checks. Native task qualification remains separate. [Receipt and next steps](docs/development.md#cw-1-saved-revision-compile-handoff--october-29-2026).

**Add to Compose** carries the exact selected saved revision from Skills into Compose after a native read, including historical revisions. Existing inputs and drafts remain intact; unsaved edits, open Compose drafts, busy/unavailable states, duplicate pins and full selections explain why adding is blocked. Draft creation, preview and save remain explicit. Late navigation/selection/Lock replies are discarded. This is source-tested; rendered and native qualification remain open. See the [implementation receipt](docs/development.md#next-02a-saved-revision-compose-handoff--november-1-2026).

Saved Compose results now open their **exact saved revision** in Skills after native readback, with matching editor focus. Later revisions are not substituted. Unsaved edits for that skill block opening; other drafts remain. Failed or stale reads keep the current workbench. [Source evidence and remaining rendered/native gates](docs/development.md#next-02b-exact-saved-result-continuation--november-1-2026).

Agent files already has bounded native folder metadata selection, source inspection and IDE-style Markdown review. Folder rows still require a separate explicit file selection to inspect content; persistent tags/indexing, remote transport and copying/applying instructions remain future work. The immediate completion order is a repeatable isolated native workflow, safe row-inspection custody, then one qualified external target. A custom executor, scheduler or larger demonstration catalog is not required for that local milestone.

## Engineering checkpoint — October 18, 2026
Expand Down
2 changes: 2 additions & 0 deletions apps/desktop/native-encrypted-qualification/tauri.conf.json
Original file line number Diff line number Diff line change
Expand Up @@ -33,6 +33,8 @@
"allow-begin-workspace-close",
"allow-acknowledge-workspace-purge",
"allow-select-and-analyze",
"allow-select-and-inspect-sources",
"allow-select-and-list-sources",
"allow-list-snapshots",
"allow-save-analysis",
"allow-open-snapshot",
Expand Down
40 changes: 38 additions & 2 deletions apps/desktop/src/native_encrypted_qualification.rs
Original file line number Diff line number Diff line change
Expand Up @@ -64,6 +64,8 @@ mod macos {
"allow-begin-workspace-close",
"allow-acknowledge-workspace-purge",
"allow-select-and-analyze",
"allow-select-and-inspect-sources",
"allow-select-and-list-sources",
"allow-list-snapshots",
"allow-save-analysis",
"allow-open-snapshot",
Expand Down Expand Up @@ -229,6 +231,8 @@ mod macos {
nonce: String,
#[serde(rename = "casePlanSha256")]
case_plan_sha256: String,
#[serde(rename = "folderFixture")]
folder_fixture: Identity,
directory: Identity,
roots: BTreeMap<String, Identity>,
}
Expand Down Expand Up @@ -350,7 +354,13 @@ mod macos {
}
impl Run {
fn validate(&self) -> Result<(), ()> {
if !same_directory(&self.directory, &self.manifest.directory) {
if !same_directory(&self.directory, &self.manifest.directory)
|| self.manifest.folder_fixture.uid != self.manifest.directory.uid
|| !same_directory(
&self.directory.join("folder-fixture"),
&self.manifest.folder_fixture,
)
{
return Err(());
}
for (name, id) in &self.manifest.roots {
Expand Down Expand Up @@ -405,7 +415,7 @@ mod macos {
return Err(());
}
let manifest: Manifest = read_record(&directory.join("manifest.json"), meta.uid())?;
if manifest.schema != "rangoon.e1c4.run.v2"
if manifest.schema != "rangoon.e1c4.run.v3"
|| manifest.nonce != args[0]
|| manifest.case_plan_sha256 != plan_digest()
|| manifest.roots.len() != plan.roots.len()
Expand Down Expand Up @@ -1119,6 +1129,32 @@ mod macos {
#[cfg(test)]
mod header_tests {
use super::*;
#[test]
fn folder_qualification_permissions_are_exact_and_required() {
let config: Value = serde_json::from_str(include_str!(
"../native-encrypted-qualification/tauri.conf.json"
))
.unwrap();
assert!(valid_context(&config, true));
for required in [
"allow-select-and-inspect-sources",
"allow-select-and-list-sources",
] {
let mut changed = config.clone();
changed["app"]["security"]["capabilities"][0]["permissions"]
.as_array_mut()
.unwrap()
.retain(|permission| permission != required);
assert!(!valid_context(&changed, true));
}
let mut broadened = config.clone();
broadened["app"]["security"]["capabilities"][0]["permissions"]
.as_array_mut()
.unwrap()
.push(json!("allow-send-cloud-model"));
assert!(!valid_context(&broadened, true));
}

#[test]
fn header_callback_accepts_only_finite_classifications() {
assert_eq!(header_reply("\"pending\""), Ok(HeaderReply::Pending));
Expand Down
Loading
Loading