Fine-tuned from Qwen/Qwen2.5-1.5B-Instruct with QLoRA for grounded patrol operational narratives used by the POLARYS analytics module (Ermita PS-5).

Intended use

Turn verified patrol aggregates / fact blocks into concise command narratives (Daily, Weekly, Area Performance, Hotspot Summary, Officer/unit volume, Operational Narrative).
Decision-support only. Does not approve, reject, modify, or delete patrol records.

Critical policy (no invention)

The model must use only facts present in the user-provided verified data block. If a fact is missing, it should say the information is not in the data / insufficient verified data.

Training data

Programmatically synthesized instruction pairs from cleaned POLARYS_DATASETS.csv patrol rows (WHAT / WHEN / WHERE / REMARKS). Targets are deterministic restatements of provided aggregates — not free-form teacher hallucinations. Includes refusal-style examples for missing metrics.

WHO/PII is omitted or reduced to unit/sector labels in training text where applicable.

How to prompt

System: You are POLARYS... Use ONLY the verified facts...
User:
Report type: Daily
...
VERIFIED DATA:
- total_patrol_activities: 42
...
Write a concise grounded narrative using only the verified data above.

Limitations

Small source CSV; behavior is summarization of supplied facts, not open-world policing knowledge.
Not a substitute for official blotter verification or command judgment.

BucDevGin/Polarys

POLARYS Report Generator

Intended use

Critical policy (no invention)

Training data

How to prompt

Limitations

BucDevGin/
Polarys