letsmakeanaiagent/CRAIGBUILT-IN EXAMPLE
● LLM-free · browser-localHelp ↗

COBOL RULES ARTICULATION ILLUSTRATION GENERATOR

Business rule explorer

Extract the statements. Trace the conditions. Keep the evidence.

Extracted rules
0
Assignments, calculations, output & calls
Data definitions
0
With original file and line references
Human review
0 / 0
Interpretation marks · not equivalence proof
Analysis gaps
0
Unsupported syntax and missing context
Live deterministic analysis. Rules describe lexical conditions and source statements for the supported subset. Runtime behavior and business intent require validation.

Rule catalog 0 rules

Source-order catalog

0 programs

A rule records a recognized source action and its enclosing IF/EVALUATE conditions. It does not infer prior values, paragraph reachability, or business policy intent.

Bring your COBOL into focus.

Add programs and copybooks, paste source, or edit files here. Analysis runs in your browser.

Project files

0
0 lines
Original source line numbers are preserved.
Project files stay in memory unless you explicitly save or export.

Limits: 60 files, 2 million characters total, 180,000 tokens per file. Convert EBCDIC to UTF-8 before import. Unsupported continuation/directive forms are flagged; see Help.

Data dictionary

Definitions are read from source and resolved plain copybooks. Field names remain literal; business descriptions are yours to verify.

Program / fieldLevel / PIC / usageValue / layoutUsed in rulesSource

Dependency inventory

Plain COPY references are expanded. CALL and PERFORM relationships are recorded; callee side effects and execution paths are not inferred.

FromRelationshipTargetStatusEvidence

Illustrate a rule

A visual path through the selected rule's lexical guards and source action. This is not a whole-program control-flow graph.

Boundary test candidates

Generated for explicit, simple field-to-number comparisons with basic numeric PIC definitions. Candidate values use exact decimal arithmetic.

Generated, not executed.These are isolated predicate cases. They do not establish whole-program outcomes or validate COBOL storage, rounding, overflow, file I/O, and external calls.
Case / rulePredicateField inputExpected predicateRuntime status

Next verification step

Run representative inputs against the original COBOL compiler and runtime. Capture output records and side effects, then compare any translated implementation using the same inputs. CRAIG does not execute COBOL.

Make the unknowns visible.

These findings limit the interpretation of extracted rules. Supply dependencies or compiler-preprocessed source where requested.

Supported subset ↗
Gap / severityConstructFindingSource

A gap-free report still reflects a lexical subset analysis, not compiler acceptance or proof of semantic completeness.