This E29 draft exposes software-factory/owner-policy from the private package. It records caller-reported asks, answers, minutes and weekly notes in a caller-owned SQLite journal. No Portfolio registry, repository, provider or scheduler is needed. It was accepted locally on 1 October 2026 (owner-designated acceptance reviewer, after independent Opus 5.5 and Fable 5.1 reviews); the complete adoption gate remains open.
Use an owned journal and clock
Install the reviewed private tarball as described in Journal adoption. The proved environment is Node.js 26.8.1 on macOS 27 arm64. The public declarations require no Node type package. The existing Journal filesystem limits and Owner policy bounds still apply.
import { CommandJournal } from 'software-factory/command-journal';
import { AskLedger, type Count } from 'software-factory/owner-policy';
const journal = CommandJournal.open('/caller/private/owner.sqlite');
let instant = Date.parse('2026-10-05T10:00:00.000Z');
const ledger = new AskLedger(journal, { now: () => instant });
ledger.recordChannels({
revision: 1, zone: 'Europe/London', live: true,
channels: [{ id: 'caller', writes: true }], recordedBy: 'owner',
});
// A fixed-clock example; real callers supply their own clock and reported ask.
instant += 1_000;
ledger.recordAsk({
askId: 'label-one', kind: 'agent-question', channel: 'caller',
askedAt: new Date(instant).toISOString(), subject: 'Which label should we use?',
productId: 'my-app', effects: [], minutes: null, recordedBy: 'caller',
});
const asks = ledger.listAsks({ productId: 'my-app' });
journal.close();
The clock is synchronous and caller-owned: now(): number returns whole milliseconds since the epoch. Replacing it requires no consumer change. Import and construction start no scheduler and read no host clock. Opening or recording is explicit. This is no authentication boundary.
LEDGER_AGGREGATE is the fixed ID owner-policy:ledger, so one journal holds exactly one ledger. Two AskLedger instances over the same journal read and write the same ledger; nothing scopes a ledger to an owner, a team or a Product within a journal. Give each owner, and each successor ledger, its own journal file. Several ledgers in one journal is an open E29 gap, not a supported layout, and nothing yet migrates a ledger between journals.
Preserve meaning and replay
The ledger preserves sf-ask-ledger/1, command identities, stored periods, receipts and bounds. Repeating a command with the same content returns its recorded receipt; changed content conflicts. A refusal records nothing. Reopening reads and checks stored state; corruption is refused without repair. Recorded rules are the owner's words and are never applied.
Counts remain exact, partial with atLeast, or unknown with reasons; unknown never establishes zero. The recorded channel list cannot reveal an omitted channel that never writes. Self-reported time and minutes are not authenticated. Future or disagreeing clocks retain the existing partial-count rules. See the Owner policy contract for settlement, KR1 windows, error order and limits.
Calendar arithmetic is shared through an internal neutral helper. Lifecycle schedule retains its public functions and exact ScheduleError class through compatibility wrappers. Owner policy retains the historical ScheduleError from the earliest ISO-week edge: week("1970-W01"), listAsks({ week: "1970-W01" }) and recordNote with week "1970-W01" throw it and write nothing; the failed date is not newly accepted. software-factory/owner-policy re-exports that class and its ScheduleErrorCode type, so a caller can catch it without importing the scheduling runtime. It is the same class software-factory/lifecycle-schedule exports, so instanceof agrees across both entry points:
import { AskLedgerError, ScheduleError } from 'software-factory/owner-policy';
try {
ledger.week('1970-W01');
} catch (error) {
if (error instanceof ScheduleError) console.log(error.code); // 'INVALID': the week begins before 1970
else if (error instanceof AskLedgerError) console.log(error.code);
else throw error;
}
Native date-range errors retain their existing behaviour. Stored periods are never recomputed as a migration. Host ICU time-zone data remains a declared dependency.
Draft proof
The external consumer uses only public imports and owned disposable journals. It proves typed passive imports without loading Portfolio or the scheduling runtime, useful recording, clock substitution, separate-process replay/reopen, refusal, corruption, file isolation and Factory-source compatibility. Fixtures captured before extraction preserve all journal rows and reports across London's 335-hour spring and 337-hour autumn baseline windows and the W53/W01 boundary. A separate baseline covers Lord Howe's half-hour transitions, Apia's skipped date, validation order and exact legacy errors.
The source distribution checks retain these proofs. Draft evidence records the exact artefact and remaining gates. No live asks, source migration, rule application or publication is established.
