|
1 | 1 | # Integrations |
2 | 2 |
|
3 | | -This repo ships twenty-three packages that **work on their own** but are **designed |
| 3 | +This repo ships twenty-five packages that **work on their own** but are **designed |
4 | 4 | to compose**. The planned cross-package compositions listed here are already |
5 | 5 | shipped, so this file now serves as: |
6 | 6 |
|
@@ -282,6 +282,31 @@ tracker files. |
282 | 282 |
|
283 | 283 | --- |
284 | 284 |
|
| 285 | +## 20. `iso-prioritize` ← deterministic priority queue selection for domain packages — **DONE** |
| 286 | + |
| 287 | +Introduced as a standalone package. `iso-prioritize` does not import JobForge, |
| 288 | +`iso-score`, `iso-timeline`, `iso-preflight`, or any other domain package; it |
| 289 | +provides the on-disk JSON prioritization config, item, and result formats that |
| 290 | +domain tools can share. JobForge-style examples cover follow-up, pipeline, and |
| 291 | +apply queues with weighted criteria, skip gates, adjustments, and one-per-company |
| 292 | +quotas, but the package remains generic: rank, gate, quota, select, check, and |
| 293 | +verify local work queues without asking a model to re-sort growing worklists. |
| 294 | + |
| 295 | +--- |
| 296 | + |
| 297 | +## 21. `iso-lineage` ← deterministic artifact freshness for domain packages — **DONE** |
| 298 | + |
| 299 | +Introduced as a standalone package. `iso-lineage` does not import JobForge, |
| 300 | +`iso-cache`, `iso-index`, `iso-facts`, `iso-preflight`, or any other domain |
| 301 | +package; it provides the on-disk JSON lineage graph format that domain tools |
| 302 | +can share. JobForge-style examples cover reports and generated PDFs derived |
| 303 | +from CV/profile/JD inputs, but the package remains generic: record artifact |
| 304 | +inputs, verify content-derived graph/record ids, check freshness, list stale |
| 305 | +outputs, and propagate stale upstream state without asking a model to inspect |
| 306 | +project history. |
| 307 | + |
| 308 | +--- |
| 309 | + |
285 | 310 | ## Design questions that are *not* open integrations |
286 | 311 |
|
287 | 312 | The following look like integrations but are deliberately decoupled — |
@@ -349,6 +374,15 @@ don't "fix" them without a conversation first. |
349 | 374 | extraction, source precedence, business calendars, stale-action retention, |
350 | 375 | and whether due actions route to prompts, ledgers, notifications, or |
351 | 376 | workflow dispatch. |
| 377 | +- **`iso-prioritize` does not decide what a domain values most.** It evaluates |
| 378 | + configured queue policy. Domain packages still own item extraction, source |
| 379 | + precedence, priority dimensions, quota policy, and whether selected items |
| 380 | + route to preflight, timelines, ledgers, notifications, or workflow dispatch. |
| 381 | +- **`iso-lineage` does not decide when a stale artifact should be rebuilt.** It |
| 382 | + detects changed source inputs and stale upstream artifacts. Domain packages |
| 383 | + still own rebuild policy, which generated files are disposable, how lineage |
| 384 | + records are created, and whether stale output blocks dispatch, triggers |
| 385 | + regeneration, or only warns. |
352 | 386 | - **`iso-postflight` does not decide how a domain collects observations.** |
353 | 387 | It settles explicit plan/outcome/artifact/step records. Domain packages |
354 | 388 | still own whether those observations come from TSV files, ledger events, |
|
0 commit comments