# Open decisions and questions for NLS

The items below remain unresolved by the supplied materials. Suggested decision partners describe the kind of authority needed; they are not assignments made by NLS. Do not mark an item resolved without a written answer, accepted test result or other attributable evidence.

## Decisions that affect the architecture

| Question | Why it matters | Evidence needed and suggested decision partner |
|---|---|---|
| Which editions and precedence govern the 2002/2005 conflict and current-version language? | Changes XML structures, limits and test rules. | Approved profile matrix from the contracting/technical authority. |
| Which multimedia types are required at acceptance? | `audioNCX` and synchronized full text imply different outputs. | Supported output-type list and reference books from NLS production/QA. |
| Which encoder, protector, validators and keys will NLS provide? | Determines the feasible encoding/protection route and deployment platform. | Current packages, versions, terms, headless interfaces, OS support and cloud approval. |
| What accompanies commercial recordings? | Metadata and matching text determine recoverable structure and pages. | Representative source sets and expected navigation from NLS production. |
| How do mastering rules apply to synthetic audio and generated labels? | Native model rate, initial-recording language and copied heading rules may conflict with a chosen workflow. | Approved interpretation and accepted synthetic example from NLS audio/QA. |
| What security controls and retention rules apply? | Determines network, access, key, logging and deletion design. | Missing Section H and approved architecture requirements from Library security. |
| What constitutes an accepted book? | Controls quality thresholds, human review and pricing/effort assumptions. | Content classes, language scope, player matrix, defect thresholds and throughput/turnaround targets. |
| What is the final submission interface for this project? | The public Transfer Portal and proposed internal S3 staging are different interfaces. | Integration contract, credentials/process ownership and acknowledgement semantics. |
| How are third-party model, voice and component rights handled? | Library ownership/non-subscription terms must coexist with component rights. | Approved inventory and applicable license/voice permissions from appropriate procurement/legal reviewers. |

## Specific mastering clarification

The live public mastering page is **1202:2026, revision 1.5, June 3, 2026**. It specifies initial 44.1 kHz PCM and adds integrated loudness of −22 LUFS ±2; it also says heading clips are copied from primary audio. The public index still advertises a 2025 entry. Confirm the actual governing edition and how these rules apply to neural synthesis and separately generated navigation speech. Resampling a model's output alone does not settle the “initially recorded” interpretation. [Current mastering page](https://www.loc.gov/nls/who-we-are/guidelines-and-specifications/contract-specifications/audiobook-mastering/) and [specification index](https://www.loc.gov/nls/who-we-are/guidelines-and-specifications/contract-specifications/).

## Additional source gaps

The SOW mentions 1201; J1 references 1208 for commercial-audio masters; only 1203 is among the four attachments. Request the complete applicable specification set. The phrase “and D standards” in SOW §3 is unexplained. The kickoff start trigger differs between §4.1 and §5.2. These are useful clarification items, not grounds to invent a preferred interpretation.

## Proposed decision record

For each answer, store the exact question, governing source and section, answer date, responsible authority, evidence link, affected profile/version, affected tests and remaining conditions. Preserve superseded decisions as history.

Example: approving a new file-count rule updates the output profile and the corresponding validator. It should not quietly change an already submitted book or erase the rule used for its original build.

## What can proceed while answers are pending

Build the source-preserving data model, importer experiments, independent quality checks and model evaluation harness. Prototype against a clearly labeled provisional profile. Avoid committing to a production codec/protection stack or promising numerical quality/throughput until the relevant components and acceptance rules are confirmed.