Extraction result

In batch mode, the Interpreter writes extraction-result.json plus a generated Screenplay .play file expressing the same provisional model. Service mode instead returns both values in a SessionResult from GET /sessions/{prologueId}/result. This page documents the extraction-result shape.

Shape

ExtractionResult

Property	Type	Purpose
prologueId	guid	Which Prologue these captures belonged to
systemName	string	Empty without a derived name; language-model refinement can propose one
modules	array of ExtractedModule	The top-level structure the Interpreter inferred

ExtractedModule

Property	Type	Purpose
name	string	Module name
description	string	Optional description
features	array of ExtractedFeature	Features within the module

ExtractedFeature

Property	Type	Purpose
name	string	Feature name
description	string	Optional description
subFeatures	array of ExtractedFeature	Nested features, when the evidence groups naturally into sub-areas
slices	array of ExtractedSlice	Slices within the feature

ExtractedSlice

Property	Type	Purpose
name	string	Slice name
type	"StateChange" | "StateView" | "Automation" | "Translation"	Candidate slice type; the current deterministic analyzer produces the first three types
description	string	Optional description
commands	array of ExtractedCommand	At most one, for a StateChange slice
events	array of ExtractedEvent	The facts the slice produces
readModels	array of ExtractedReadModel	For a StateView slice
projections	array of ExtractedProjection	How read models are built from events
constraints	array of ExtractedConstraint	Candidate uniqueness constraints inferred from captured database schema

commands is a list rather than a nullable single value — a StateView/Automation/Translation slice simply has an empty list, so the shape never carries a null.

ExtractedCommand, ExtractedEvent, ExtractedReadModel

Property	Type	Purpose
name	string	Type name
description	string	Optional description (commands only)
properties	array of ExtractedProperty	The fields on this type
validations	array of ExtractedValidationRule	Command-only — see below

ExtractedProperty: name, type, isRequired (bool), maxLength (int, 0 when not applicable).

ExtractedProjection and ExtractedConstraint

Type	Properties
ExtractedProjection	name, sourceEvents (array of event type names the projection consumes)
ExtractedConstraint	name, property, onEvent (which event’s property the constraint governs)

ExtractedValidationRule

Property	Type	Purpose
property	string	Which command property the rule applies to
kind	"Required" | "MaxLength" | "MinLength" | "Pattern"	The kind of validation the evidence implied
argument	string	The rule’s argument (a length, a pattern)
message	string	The message associated with a rejection

What happens to it next

The generated .play file is a provisional starting point, not accepted intent. Review and correct its domain terms and boundaries, validate it with the applicable Screenplay compiler/profile, and verify its behavior before using it as model input.

Next

• How Prologue works — how the Interpreter derives this structure from captures.
• Screenplay — the language this result compiles into.