@velinussage/locus-agent-skill 0.1.27 → 0.1.29

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@velinussage/locus-agent-skill",
3
- "version": "0.1.27",
3
+ "version": "0.1.29",
4
4
  "description": "Install the general Locus agent skill, the surrounding-area purchase workflow, and the property-tax protest workflow for free and x402-paid property context.",
5
5
  "type": "module",
6
6
  "bin": {
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  name: locus-agent-tools
3
3
  preamble-tier: 1
4
- version: 1.42.0
4
+ version: 1.44.0
5
5
  description: Use every time the task is a US address or place and you need cited official public records or local-government context — due diligence, flood, zoning, permits, taxes, what changed, or before you sign.
6
6
  triggers:
7
7
  - property due diligence
@@ -342,7 +342,7 @@ Use these only after `locus_lane_availability` or the paid index says the call h
342
342
  | `POST /api/locus-valuation-challenge` | `$0.10` | Agent wants to stress-test a caller-supplied property price or `source: "assessment_notice"` figure against cited sale, parcel, permit, hazard, tax, zoning, policy, and same-roll assessment-uniformity evidence without Locus creating a price. | Fewer than two substantive cited sections return `charged:false`; uniformity needs at least five same-class parcels to count. |
343
343
  | `POST /api/locus-road-access` | `$0.05` | Agent needs nearest mapped public-road proximity from an address/point as an early access screen. | Unresolved address or total source failure returns `charged:false`. Never a legal-access, easement, frontage, or landlocked determination. |
344
344
  | `POST /api/locus-assessment-position` | `$0.10` | Owner or agent asks where a tax assessment sits among similar properties on the same roll, the appeal deadline rule, and how to file. No dollar figure required. | Charged only when the same-roll sample is substantive; unresolved address or thin sample returns `charged:false` with the deadline rule and filing guide still attached. Descriptive percentile only; never a determination of over-assessment or advice to appeal. |
345
- | `POST /api/locus-practitioner-read` | `$0.49` | Agent wants what an experienced land and property analyst reads into the public records for one address: which patterns are present (repeat transfers, permit with no closeout, flood zone next to county claims history, zoning headroom, soil limits, enacted vs pending ordinance), the record that confirms each, and one plain-language summary. Optional `question` sets the audience. | Flat price on every call; an empty reading set is still paid. Readings are framings to test with a named confirming record, never findings; no value, no safe/unsafe, nothing about a person. `partial` names the record Locus does not carry (deed type, parcel-level liens, panel revision history). Unresolved address, engine outage, or a prose guardrail failure returns `charged:false`. |
345
+ | `POST /api/locus-practitioner-read` | `$0.29` | Agent wants what an experienced land and property analyst reads into the public records for one address: which patterns are present (repeat transfers, permit with no closeout, flood zone next to county claims history, zoning headroom, soil limits, enacted vs pending ordinance), the record that confirms each, and one plain-language summary. Optional `question` sets the audience. | Flat price on every call; an empty reading set is still paid. Readings are framings to test with a named confirming record, never findings; no value, no safe/unsafe, nothing about a person. `partial` names the record Locus does not carry (deed type, parcel-level liens, panel revision history). Unresolved address, engine outage, or a prose guardrail failure returns `charged:false`. |
346
346
  | `POST /api/locus-power-water-evidence-pack` | `$0.05` | Agent needs pre-development proximity/context from HIFLD/EIA power, EPA public-water-system, and FCC broadband sources. | Missing substantive evidence suppresses charge. Never claims capacity, interconnection, service availability, timing, or cost. |
347
347
  | `POST /api/locus-landslide-diligence` | `$0.05` | Agent needs separate USGS documented inventory history and exact source-native n10 model-cell evidence. | Unless both components answer, returns `charged:false`. Never a probability, parcel stability finding, engineering assessment, or safety label. |
348
348
  | `POST /api/locus-permit-closeout-check` | `$0.05` | Agent needs exact-subject permit status plus source-published closeout or occupancy-document evidence. Registry coverage: Raleigh, unincorporated Wake County, Durham, Austin, Seattle, Chicago, Los Angeles, and New York City. It accepts an address or up to 25 jurisdiction-scoped `parcelIds`. The coverage label is generated from the source registry. | Uncovered, uncertain, unavailable, unpublished, and no-exact-match states are charge-suppressed. Not condition, compliance, suite/use permission, or closing approval. |
@@ -579,7 +579,7 @@ When the owner already has a figure to test, use `locus-valuation-challenge` wit
579
579
 
580
580
  ### 4. "What would an experienced analyst read into all of this?"
581
581
 
582
- One paid call: `POST /api/locus-practitioner-read { "address": ..., "question": optional }` ($0.49
582
+ One paid call: `POST /api/locus-practitioner-read { "address": ..., "question": optional }` ($0.29
583
583
  flat). Locus fetches its own records (parcel, transfers, zoning, rezonings, permits, flood,
584
584
  county flood claims, wetlands, soil, capital projects, legislation, area tax distress,
585
585
  assessment position), builds typed facts from them, selects the catalogue readings those facts
@@ -591,6 +591,21 @@ instead of them: the readings point back to the same cited records. Never quote
591
591
  finding; the wording is "worth checking against", and the record named in `checkNext` is the
592
592
  thing to open next.
593
593
 
594
+ The response also carries `permitMix` for covered metros (Raleigh and Durham today): permit
595
+ counts by class for the last 12 months and the 12 before (new building, new dwelling,
596
+ addition, alteration, demolition, change of use, accessory), a heavy-use list (permits whose
597
+ recorded use maps to data_center, substation, industrial, or warehouse, with cost as filed and
598
+ the record id, never an address), and data-quality shares. Six readings sit on top of it:
599
+ new-construction increase, new-construction slowdown, heavy-use permit on file, same-parcel
600
+ demolition then new building, demolition without replacement, and change-of-use rise. Each
601
+ cites its two-window counts; "up from 3 to 9" is the wording, never "booming" or
602
+ "transitioning". `waterContext` is a separate section keyed to the water system that serves
603
+ the address (PWSID), with violation rows by type and date, a PFAS count with its gap note, and
604
+ a standing non-inference line: water records are system-wide, not this address, and Locus
605
+ draws no conclusion about capacity, quality, or the effect of any permitted use. Outside a
606
+ covered metro, `permitMix.available` is false and the six readings are listed under
607
+ `readingsNotEvaluated`.
608
+
594
609
  ## A2A call shape
595
610
 
596
611
  ```json