LexLint

Know the law your code answers to.

RunPack In development

The declaration you and counsel agreed, in production. The agent works only where and how it was agreed, and every action leaves evidence.

Only where it was agreed A world map of Pennant's approved declaration, with its collections agent in the Atlantic. Its text to a debtor in Colorado is sent. Its text to a debtor in Brazil, which the declaration leaves out, is refused. The evidence record reads: 14:02, send_text, Brazil, refused, not in pennant-v3. RunPack Only where it was agreed Pennant's agent text sent refused evidence 14:02 · send_text · Brazil · refused · not in pennant-v3

For legal teams and technical teams.

Kept in scope, and recorded

agent send_text to debtor 4471, in Brazil

RunPack refused Brazil is not in pennant-v3

agent place_call to debtor 2210, in Colorado

RunPack refused place_call is voice processing, not in pennant-v3

evidence 2 records: the time, the Ruleset, the place and how it was known, the tool, the work, the decision

Modes, and changes

Strict enforces, and log records what strict would refuse, so a new Ruleset can be tried first. There is no override: a change goes back to counsel and comes out as a new version.

The lint in your coding CLI and TestPack will check for the same evidence while the code is written. What that evidence is: the Handbook's logs document and the incident clock.

In CI, TestPack checks the same version.