Skip to main content
Back to Prompt Library
implementation

Build the application

Inspect the original prompt language first, then copy or adapt it once you know how it fits your workflow.

Linked challenge: Build a BODS State-Owned Enterprise Control Chain Visualizer

Format
Code-aware
Lines
73
Sections
11
Linked challenge
Build a BODS State-Owned Enterprise Control Chain Visualizer

Prompt source

Original prompt text with formatting preserved for inspection.

73 lines
11 sections
No variables
1 code block
## Build
Parse corporate registry declarations against BODS v0.4 data standards to identify state-owned enterprise structures. Extract government control thresholds and map indirect state ownership paths.

## User
Enhanced due diligence investigator

## Workflow
1. Ingest BODS v0.4 statement packages containing entity ownership and directorship declarations.
2. Apply BODS modeling requirements to detect state-owned enterprise markers and government identifiers.
3. Calculate cumulative indirect ownership percentages to determine absolute state control thresholds.
4. Render an SOE control chain dossier detailing government influence across corporate hierarchies.

## Interface
Network visualization showing shared directorships and registered agent clusters with an evidence drill-down panel.

## Data
Generate 45 synthetic BODS records showing varying degrees of direct and indirect government ownership.
Starter examples below are synthetic. They are not downloaded records.

## Source
[Beneficial ownership modelling](https://standard.openownership.org/en/latest/standard/modelling/index.html)
Adheres to BODS v0.4 specific modeling guidance for 'Representing state-owned enterprises' cited in source excerpt 4.

## Tools
langgraph, networkx, pydantic.
LangGraph choreographs multi-step node traversal to evaluate interconnected directorship networks.
Local or hosted LLM for drafting investigative findings from raw cluster metrics.

## Deliverables
Submit runnable source, pinned dependencies, setup commands, a working interface, example outputs, and a recorded end-to-end demo. Include tests and an action log.

## Acceptance
- Correctly identifies entities designated as state-owned enterprises via BODS schema.
- Calculates cumulative ownership chains to verify absolute government control thresholds.
- Generates a structured JSON dossier outlining the state ownership path.

## Starter Examples
```json
[
  {
    "input": {
      "entity_id": "ENT-990",
      "name": "National Telecom LLC",
      "ownership_statements": [
        {
          "interested_party": "GOV-01",
          "type": "state_body",
          "shares_exact": 60
        }
      ]
    },
    "expected_output": {
      "is_soe": true,
      "controlling_state_body": "GOV-01",
      "cumulative_state_ownership": 60,
      "chain_depth": 1
    }
  },
  {
    "input": {
      "entity_id": "ENT-991",
      "name": "Local Retail Corp",
      "ownership_statements": [
        {
          "interested_party": "PER-05",
          "type": "person",
          "shares_exact": 100
        }
      ]
    },
    "expected_output": {
      "is_soe": false,
      "controlling_state_body": null,
      "cumulative_state_ownership": 0,
      "chain_depth": 0
    }
  }
]
```

## Safety
Assesses structural pattern risks; does not accuse individuals or make automated corporate governance judgments.
Use mock external writes. Require human review before any real deployment.

Adaptation plan

Keep the source stable, then change the prompt in a predictable order so the next run is easier to evaluate.

Keep stable

Hold the task contract and output shape stable so generated implementations remain comparable.

Tune next

Update libraries, interfaces, and environment assumptions to match the stack you actually run.

Verify after

Test failure handling, edge cases, and any code paths that depend on hidden context or secrets.