Back to Prompt Library
Implementation planning and evidence-linked development
Build the complete application
Inspect the original prompt language first, then copy or adapt it once you know how it fits your workflow.
Linked challenge: Build a Segment Valuation and Intercompany Elimination Workspace
Format
Text-first
Lines
51
Sections
16
Linked challenge
Build a Segment Valuation and Intercompany Elimination Workspace
Prompt source
Original prompt text with formatting preserved for inspection.
51 lines
16 sections
No variables
28 checklist items
## User A sum-of-the-parts valuation analyst. ## Build Value a multi-business company without counting internal revenue, assets, or corporate costs twice. Maintain a clear bridge from segment estimates to consolidated equity. ## Input Contract - Key: segment_id + fiscal_period + valuation_scenario. - Fields: external_revenue, internal_revenue, segment_value, corporate_cost_value, elimination_id, net_claims. - Segment totals and consolidated totals require an explicit reconciliation. ## Workflow 1. Map segments and intercompany relationships. 2. Separate external activity from internal transactions. 3. Apply documented segment valuations and corporate adjustments. 4. Export the consolidated bridge and unresolved allocation decisions. ## Interface A segment matrix with elimination links, allocation controls, and a consolidated value waterfall. ## Deliverables - A segment-to-consolidation mapping model. - A valuation workbook with elimination provenance and allocation sensitivities. - Runnable local application, setup commands, and a dependency lockfile. - Versioned input data, data dictionary, acquisition instructions, and rights notes. - Calculation traces, source references, assumption records, and exported review artifacts. - A deterministic baseline and tests for normal, incomplete, contradictory, and failure-recovery cases. - A recorded complete workflow with a reproducible manifest and explicit limitations. ## Acceptance Criteria - Internal transactions are eliminated exactly once. - Corporate costs are not omitted from all segments and the consolidated bridge. - Segment definition changes remain visible across years. - Unallocated values carry explicit uncertainty rather than fabricated precision. ## Contrast Case Keep segment estimates fixed and introduce a duplicated asset value. The corrected consolidated value falls by that duplicate. ## Dataset Scope The attached starter files are prototype inputs. Expected starter answers are visible. They are not independent holdouts. Full target: Use public segment disclosures with fictional standalone valuation estimates and explicit corporate adjustments. Preserve unallocated items instead of distributing them silently. Complete target contracts and expert review remain pending. Public observations are not historical release vintages. ## Tools DuckDB, pandas, openpyxl Use an available model appropriate to the task. Record provider, model identifier, version or retrieval date, settings, cost, and latency. Use deterministic code for calculations. Models may extract, retrieve, or explain evidence. They must not invent missing records, override approval rules, or claim professional authority. ## Constraints The application does not infer hidden segment profitability from incomplete disclosures. - No fabricated records, source citations, professional endorsements, or expert-adjudication claims. - No future-data leakage into dated decisions, model fitting, or historical valuation inputs. - No unauthorized payments, account restrictions, regulatory filings, or production changes. - No automated appraisal certification, tax-compliance determination, or unsupported fraud accusation. - No concealed uncertainty or silently invented inputs required for a numerical conclusion. ## Scoring - Correct domain calculations and justified methods with documented assumptions. Weight: 30. - Source lineage, temporal integrity, rights checks, and explicit synthetic-data labels. Weight: 25. - A working application with review, export, error handling, and reproducible state. Weight: 20. - Adversarial cases, uncertainty, missing-data behavior, and sensitivity analysis. Weight: 15. - Evidence-linked conclusions that distinguish facts, assumptions, and unresolved judgments. Weight: 10. Score each dimension from zero to two. Weighted score = sum(weight * score / 2). A failed safety gate blocks acceptance.
Adaptation plan
Keep the source stable, then change the prompt in a predictable order so the next run is easier to evaluate.
Keep stable
Preserve the source structure until you know which part of the prompt is actually driving the result quality.
Tune next
Change domain facts, examples, and tool context first before you rewrite the instruction scaffold.
Verify after
Validate one failure mode at a time so prompt changes stay attributable instead of getting noisy.