Additive profiles: Verified local snapshot. Historical receipts retain their recorded scope; live qualification and customer delivery require separate evidence.
Use the private package's software-factory/attention and software-factory/owner-digest entry points with your own facts. No Portfolio registration, Git checkout, provider or Factory coordinator is needed. These E29 additions were accepted locally on 1 October 2026 (owner-designated acceptance reviewer, after independent Opus 5.5 and Fable 5.1 reviews).
Install and project Attention
Obtain and install the private tarball using the Journal adoption guide. Node.js 26.8.1 or later is required; the demonstrated environment is macOS 27 arm64. There are no npm runtime dependencies. The package stays private, and import starts no reader, scheduler, server or sign-in.
import { projectAttention } from 'software-factory/attention';
const attention = projectAttention({
registeredProducts: 1,
products: [{
productId: 'app', displayName: 'My app',
repository: { state: 'unknown' },
blockers: { open: [] }, sourceNotices: [],
}],
usage: { state: 'ok', sourceNotices: [] },
}, { canCheckRepository: false });
console.log(attention);
This returns a repository-unchecked notice. It does not infer that anything is blocked or that the owner must act. AttentionRead, AttentionProjection, BlockerRecord and BlockerDetail are exported types. projectBlockerDetail keeps reported resolution distinct from verification. The result has no Dashboard protocol envelope.
Attention is a pure projection of typed, validated read models, not an arbitrary-JSON parser. The caller must bound and validate its readers, preserve unique Product/blocker/source identities, and resolve current source revisions before projection. Text and references remain data; never supply credentials. Projection changes no input or stored state. Source notices keep their reporting windows; only presentation is capped (five displayed windows and a 280-character unreadable detail). See the full Attention contract.
Record a digest from your own reader
import { CommandJournal } from 'software-factory/command-journal';
import { OwnerDigest, proposedDigestCommission } from 'software-factory/owner-digest';
const journal = CommandJournal.open('./owner.sqlite');
try {
const reader = {
listProducts: () => ({
version: 1, products: [{ productId: 'app', displayName: 'My app' }],
}),
readHealth: productId => ({
productId, health: { state: 'none' }, polledAt: null,
}),
readHistory: productId => ({
productId, state: 'read', events: [], more: false,
}),
readOwnerRequired: () => ({ state: 'unknown', reason: 'not read yet' }),
};
const digest = new OwnerDigest(journal, {
commission: proposedDigestCommission(),
now: () => Date.parse('2026-09-28T08:00:00.000Z'),
reader,
});
console.log(digest.formDigest());
} finally {
journal.close();
}
This records a useful short digest showing the Product's unknown health and unavailable owner-required count. Repeating it returns the same recorded weekly digest without calling the reader again. Supply the application's authorised commission and clock in real use; proposedDigestCommission is a proposal, not scheduling or delivery authority.
DigestReader exposes four synchronous methods: listProducts(), readHealth(productId, asOf), readHistory(productId, afterSequence, asOf) and readOwnerRequired(asOf). Readers return names and attributed facts, never checkout paths. An alternate conforming reader needs no consumer change. The vocabulary remains the established build-health vocabulary, with existing source citation kinds and digest wording. A reader cannot turn an assertion into an authenticated Verdict. Only set blockerMirrored after establishing that exact source revision.
The core validates supplied identities, shapes, times and bounds before writing. Duplicate registry identities, cross-Product results, owner-required coverage whose asOf differs from the requested instant, and non-advancing history are DigestError INVALID; explicit unreadability and otherwise-valid polls later than the requested instant become per-Product gaps. Supplied facts are validated before that future-poll downgrade. A reader without owner coverage at the requested instant must return unknown; stale or future counts cannot support an all-clear. Recorded /2 digests retain their original coverage and replay unchanged. Reader exceptions propagate. Each call accepts at most 100 Products and reads at most 16 history pages per Product, with at most 1,000 events per page and 50 items per event. Whole events that do not fit a batch wait for another slot. The digest refuses text over 150 words after its existing compact rendering options. Unknown never means zero or failed. The full digest contract lists quiet hours, retention, errors and all types.
Fresh green health must have a head, complete read check evidence, no failed/pending/unsettled counts, no reasons and no open episodes. At least one check or commit status must have passed. DigestHealthRead may supply an optional statuses: DigestTally for that same head; when supplied, it must also be complete and settled before green is accepted. Passing statuses cannot override unknown checks. Skipped or neutral checks may accompany a real pass. The Factory reader supplies its recorded status tally. This extra evidence is validated only on new reads and is never added to stored /2 inputs; existing records, including previously accepted contradictory inputs, remain byte-compatible and replay without rereading sources.
Fresh red health requires a failed read check, a failed supplied status, or an open-view episode with condition red. Partial failure evidence is sufficient; no known-head or complete-coverage requirement is added for red. Without that evidence both batch and digest formation refuse DigestError("INVALID") before writing, including for future polls. Historical /2 parsing and replay remain unchanged.
State, compatibility and evidence
The legacy OwnerDigest owns owner-digest:main; independent callers may select the additive presentation instance API below. The package and Factory adapter read and write the same sf-owner-digest/2 records. Stored text is re-rendered and checked on every read; corruption is refused without repair. The external consumer also reads a fixture created by the pre-extraction source at c27b643, byte-for-byte, and refuses altered text. No migration is performed.
The private package version remains 0.1.0. Its pre-1.0 compatibility policy is the Journal guide's: incompatible APIs need a new minor version and documented adoption changes; compatible fixes use patch versions. A digest rendering change needs a new persisted protocol. Keep the tarball pinned in the caller's lockfile. Private source and compiled helper paths are unexported; use only the declared entry points.
The source distribution checks run the original Journal scenarios and a separate projection consumer outside the repository. They prove passive imports under read-only Node permissions, exact loaded module closure, declarations without Node type packages, neutral provenance and unknowns, alternate readers, refusal, replay/reopen, corruption and Factory-adapter state compatibility. The fixture contains no private imports or Portfolio/Git/provider setup. See the draft evidence for the exact artefact and remaining gates. No live polling, scheduling, delivery or public publication is established.
Factory-specific parts
The legacy OwnerDigest and renderDigest contracts retain these fixed names. Source citations here refer to 85a5472:
- The heading is
Factory digest, week of <date>.(src/owner-digest-core.ts:535). - The aggregate is
owner-digest:main(src/owner-digest-core.ts:33) and the state protocol issf-owner-digest/2(src/owner-digest-core.ts:31). - Citation kinds include
portfolio-conditionsandregistry(src/owner-digest-core.ts:244-245,src/owner-digest-core.ts:548-552). These name retained facts, not authority.
Every stored digest must re-render identically (src/owner-digest-core.ts:925-931). Changing legacy persisted wording or identity needs a new protocol version and an explicit reader. The separate sf-owner-digest-presentation/1 profile below supplies caller presentation without relabelling old records.
Caller-owned presentation and identity
OwnerDigestPresentationV1(journal, {...options, aggregateId, presentation}) requires the same reader, clock and commission plus {protocol: 'sf-digest-presentation/1', digestLabel}. The aggregate is a bounded ASCII ID other than owner-digest:main; the label is nonempty plain text of at most 80 characters and 320 UTF-8 bytes, with controls and malformed Unicode refused. readOwnerDigestPresentationV1(journal, instance) and renderDigestPresentationV1(input) explicitly read and render the new records.
The sf-owner-digest-presentation/1 state stores immutable presentation and instance digest; every sf-digest-presentation-input/1 includes its original label. The whole rendering, including that label, counts toward 150 words. Input is refused rather than truncated. All note, batch and digest receipt IDs are instance-specific. Changed presentation on an existing aggregate refuses; choose a fresh aggregate for a different instance. A retained weekly digest replays exactly; a note retry after retention pruning can safely refuse a journal command conflict without writing.
OwnerDigest, readOwnerDigest and renderDigest keep /2 storage, the fixed Factory heading, citation kinds and original bytes. The Factory adapter continues to consume them. Neither API authenticates facts, changes old wording, repairs records or supplies scheduling/delivery authority.
