Bijou
Organizational Interests, Stateful Capability Progression & Resource Portfolio Engine (v2)
Overview
Bijou is an offline-first strategic portfolio, capability dependency, and resource orchestration engine designed for modeling the complex interactions between:
- Organizations (and managed Color-of-Money resource pools)
- Interests (hierarchical DAGs spanning mission goals, threats, intelligence gaps, customers, and strategic categories)
- Efforts (stateful capability programs with optional resource requirements, delivery risks, mitigators, and explicit or dependency-relative timing)
- 6 Typed Relationships with Pedigree (
OrgOrgEdge,OrgInterestEdge,InterestInterestEdge,OrgEffortEdge,EffortInterestEdge,EffortEffortEdge)
Bijou ships as a single PyPI distribution (bijou-portfolio, import namespace bijou) bundling the FastAPI engine, SQLite + DuckDB stores, offline Vanilla JS/SVG Web UI, CLI entrypoints (bijou, bijou-ingest), and the integrated Python client SDK (bijou.sdk).
Key Capabilities
- Three Primary Graph Modes (
A/B/G):- View A — Capability Progression Tree: Stateful Effort DAG (
COMPLETED→IN_WORK→PLANNED/DISCOVERY_PENDING) with SPOF detection, slack calculation, and hover neighborhood emphasis. - View B — Tri-Partite Architectural Flow: Maps Organizations & Pools ↔ Efforts ↔ Interest Taxonomy, illuminating indirect shared-interest benefits and potential organizational partnerships.
- View G — Global Neural Graph: Free-floating force-directed topology with pairwise AABB zero-overlap resolution, node-type toggles, Org/Interest multi-filters, node isolation (
Right-Click → Isolate & Connections), breadcrumb filter history, drag pinning, and cursor-anchored scroll-wheel zoom.
- View A — Capability Progression Tree: Stateful Effort DAG (
- Graph-Native Non-Technical Editing:
- Right-click anywhere to spawn Organizations, Efforts, or Interests; drag
●connect handles between nodes to create relationships using plain-English statements instead of raw enum/direction jargon.
- Right-click anywhere to spawn Organizations, Efforts, or Interests; drag
- Bill of Efforts Scenario Dock:
- Persistent slide-out cart for exercising mitigators, staging resource pool allocations (with Color-of-Money Interest DAG inheritance & skill-mismatch slip warnings), testing schedule slip/cancellation shocks, and committing approved decisions.
- Executive Briefing & Entity Studio:
- 1-slide landscape printable briefing tailored per Organization (
X-Bijou-Access-Mode/X-Bijou-Active-Orgperspective seam) plus a full Entity & Graph Studio with pre-flight manifest diagnostics.
- 1-slide landscape printable briefing tailored per Organization (
- Air-Gapped & Self-Contained:
- Zero external JS libraries or CDNs in the Web UI; custom pure Vanilla JS + native browser SVG/DOM rendering bundled directly into the Python wheel.
Quickstart
1. Installation
Install from PyPI (pip install bijou-portfolio) or from source:
pip install bijou-portfolio
# or from local source checkout:
pip install -e ".[dev]"
The single bijou-portfolio wheel includes the backend API, CLI, Web UI static assets (plus offline OpenAPI explorer), and bijou.sdk (keeping the bijou import namespace).
Air-Gapped / Corporate Firewall Transfer
When moving across a firewall into an internet-isolated network, gather platform-matched wheels (including compiled wheels such as duckdb and pydantic-core) on the connected side first:
# Example for Windows x64 + Python 3.12
pip download bijou-portfolio -d ./wheelhouse --only-binary=:all: --platform win_amd64 --python-version 3.12
# On the air-gapped target machine:
pip install --no-index --find-links=./wheelhouse bijou-portfolio
Note for locked-down corporate hosts: if the current directory is read-only, Bijou automatically stores its SQLite and DuckDB files in ~/.bijou/, or you can use bijou --host 127.0.0.1 / BijouDesktopBridge to avoid Windows Firewall prompts.
2. Launch the Application
# Desktop workbench (zero-webserver in-process pywebview window)
bijou --mode desktop
# Or standalone FastAPI HTTP server
bijou --mode standalone --port 8000
- Web UI:
http://0.0.0.0:8000/(orhttp://localhost:8000/in a local browser) - Offline Interactive API Explorer:
http://localhost:8000/docs(also/redoc, zero external CDNs) - OpenAPI 3.1 Schema:
http://localhost:8000/openapi.json
3. Ingest Reference Data
bijou-ingest --server-url http://0.0.0.0:8000 \
--manifest datasets/joint_isr_architecture.yaml \
--telemetry datasets/satellite_cascade_telemetry.jsonl \
--replace-all
Integrated Python SDK (bijou.sdk)
Use BijouClient (sync), AsyncBijouClient (async), and ManifestIngestor directly from bijou.sdk for document-extraction pipelines and analytical automation:
from bijou.sdk import (
AccessMode,
BijouClient,
ManifestIngestor,
Organization,
)
with BijouClient(base_url="http://0.0.0.0:8000") as client:
# Upsert entities (idempotent by string ID)
client.upsert_organization(
Organization(id="org-demo", name="Joint Demo Org", is_managed=True)
)
# Or import an atomic multi-entity manifest bundle from an extractor
ingestor = ManifestIngestor(client)
ingestor.ingest_manifest_file(
"datasets/joint_isr_architecture.json",
validate_first=True,
)
# Query projections and run Bill of Efforts simulation
tree = client.get_capability_tree()
sim = client.simulate_bill_of_efforts({"effort_slips": {"eff-edge-correlator": 30}})
print(f"Nodes: {len(tree.nodes)}, Impacted: {sim.impacted_effort_ids}")
Documentation Index
- User Guide: Domain ontology, forecasting semantics, Color-of-Money rules, and UI walkthrough.
- Architecture Specification: Hexagonal architecture, SQLite/DuckDB persistence, NetworkX projection engine, and custom SVG/DOM rendering.
- Developer & Contributing Guide: Setup, test suites, banned-token / offline compliance audits, and wheel packaging.
- API & SDK Reference: Complete REST endpoint catalog,
bijou.sdkmethods, models, exceptions, and CLI flags.
Testing & Quality Assurance
# Run full suite (unit, contract, adversarial, SDK, ingest, Selenium E2E, wheel check)
pytest tests -v
# Audit source code for banned tokens
python scripts/audit_banned_tokens.py
# Run pre-flight gate
python scripts/black_preflight_audit.py --root .
# Regenerate static OpenAPI schema snapshot
python scripts/export_openapi.py
License
This project is licensed under the MIT License — see LICENSE.
Metadata
Release files for bijou-portfolio 2.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| bijou_portfolio-2.0.2.tar.gz | 164.2 kB | With provenance | Details for bijou_portfolio-2.0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| bijou_portfolio-2.0.2-py3-none-any.whl | Python 3 | none | any | Details for bijou_portfolio-2.0.2-py3-none-any.whl |
Total release size: 348.0 kB
Release files / bijou_portfolio-2.0.2.tar.gz
| Download URL | bijou_portfolio-2.0.2.tar.gz |
|---|---|
| Size | 164.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8ab0c985e6c21d4edcb3e6c52b02c03a224384525f6f4c6fdab839b9459728b9
|
|
BLAKE2b-256 checksum How to use checksums |
f11ce808d8f2a76f8816702a3123101e15956f565715cb10d4ffaa3adfe1d413
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.
Transparency logRelease files / bijou_portfolio-2.0.2-py3-none-any.whl
| Download URL | bijou_portfolio-2.0.2-py3-none-any.whl |
|---|---|
| Size | 183.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bf967404befec783b7fd3faa8a60cc1b94ef23d32c7e5a6d7e9ba92e82b67ca0
|
|
BLAKE2b-256 checksum How to use checksums |
6cb6b23411d4b789082c1a92bf19d32487b649adce7ba2f5ecbca8e3c6eec48c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.
Transparency logSecurity for bijou-portfolio 2.0.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for bijou_portfolio-2.0.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.