appshare

Reference apps

Copy the golden path before inventing a stack.

These examples show the frontend lane, server-side function boundary, runtime policy, data schema, import mapping, and publication payload expected from appshare mini apps.

Use this with Codex

Point the agent at `/llms.txt`, choose a project and `dev` environment, then reuse the closest example structure. Promote to `prod` only after reviewing policy, data, and publication access.

Bootstrap SDK Functions

Pending incidents

A master list for pending legal incidents. Business filtering runs in a Project Function, not in browser JavaScript, and PII fields are marked in the table schema.

  • Runtime policy with `admin`, `legal`, and `guest` profiles.
  • Folder gating through `allowed_runtime_roles`.
  • `table_import` payload with explicit field mapping.
Open implementation notes
React Closed stack

React lane

Use only the bundled React kit and approved dependencies for complex stateful apps. Generate project SDKs instead of hand-writing DTOs and API calls.

  • Good for dense dashboards and advanced workflows.
  • Requires stricter component and dependency control.
  • Documented in the React LLM lane.
Open React lane
Vanilla Bootstrap

Default lane

Start with HTML, vanilla JavaScript, Bootstrap theme, Appshare SDK, and the custom searchable combobox. This is the default for most internal forms and master-detail tools.

  • No build step required for small apps.
  • Works directly against server-side `dev` services.
  • Designed for Codex-generated frontends.
Open Bootstrap lane
1. Scaffold

Copy the nearest example structure and set `projectId` plus `environment=dev`.

2. Configure

Create schema, runtime policy, functions, imports, and publication folder access.

3. Verify

Run through the app with admin and restricted profiles. Check audit logs for PII access.

4. Promote

Publish reviewed files to prod with explicit promotion. Do not write prod data from dev.