Download the complete part-06 practice pack (ZIP). Extract it and preserve its folders. All organizations, records, and results in this teaching pack are fictional.
All Cedar Desk Studio, Pine Supply, product, demand, price, inventory, and support examples are fictional. Nothing has been sold, published, ordered, or changed in a live commerce system. The included Job Log Starter Kit is a draft teaching prototype, not a commercial release.
1. Offer and validation brief
Intended user and buyer:
Recent problem and evidence:
Existing workaround and alternatives:
Proposed deliverable and useful task:
What the offer does not include:
| Assumption | Current evidence | Smallest honest investigation | Decision rule | Cost and owner | Remaining limit |
|---|---|---|---|---|---|
Actual offer shown, permitted action, and relevant terms:
Eligibility, denominator, observation window, and exclusions:
Observed findings and decision:
Practice: practice/offer-funnel.json has 120 constructed visitors, 18 sample requests, and nine interest-list signups. All signups are a subset of sample requesters. No purchase was offered. practice/offer-economics.json describes assumed contribution and development cost, not revenue or demand.
2. Catalog change proposal
Seller SKU / supplier SKU / variant / sellable unit:
Source, timestamp, permissions, and source owner:
| Field or claim | Current value | Proposed value | Supporting source | Missing information | Reviewer decision |
|---|---|---|---|---|---|
Pre-application recheck: Source identity, current cost/stock, unit, currency, latest approved values
Application result and customer-facing verification:
Practice: Use practice/Commerce-Sources.md, practice/catalog-cases.csv, and practice/box-12-record.json. The item is a five-box pack with external dimensions. No internal fit, acid-free certification, or numeric supplier quantity is supplied. Proposed updates remain unapproved.
3. Price and availability worksheet
Currency / fee basis / rounding / taxes included or excluded:
| Cost input | Amount or rule | Evidence date | Measured or assumed | Review owner |
|---|---|---|---|---|
| Product cost per sellable unit | ||||
| Shipping and packaging | ||||
| Transaction and channel fees | ||||
| Returns and support | ||||
| Other variable costs |
Target contribution, candidate price, and forward check after rounding:
Separate market acceptance evidence:
Stock field definitions / locations / source dates:
Physical stock − non-overlapping reservations, damage, and buffer:
Incoming stock / supplier availability / unresolved quantities:
Practice: practice/price-assumptions.json yields $7.13 contribution at $29 and $8 at $29.90 under the listed assumptions. practice/inventory.json yields four available-to-promise packs; incoming five packs are excluded. Supplier availability is a flag with unknown quantity.
4. Digital product specification and rights record
User's target task:
Format, files, prerequisites, and supported environments:
Data fields and meanings:
Required behavior and explicit limitations:
Blank asset / worked example / first-use instructions:
| Asset | Origin and contributor | Permission/license evidence | Distribution scope | Outstanding issue |
|---|---|---|---|---|
File checks performed and result:
Usability and accessibility evaluations performed or pending:
Owner review and commercial release decision:
Practice: Open practice/job-log-starter/User-Guide.md. It explains the blank and example CSVs. The files do not enforce their written rules or send reminders. practice/job-log-invalid-cases.csv contains deliberately invalid rows for file validation practice and is not a user working file. practice/rights-record.csv does not assert a completed commercial licensing decision.
5. Product lifecycle plan
Product/version and exact delivered files:
Offer, update entitlement, support availability, and customer terms:
Approved support route and case owner:
Release checks, owner approval, and actual delivery evidence:
Proposed change, affected versions, and customer action required:
Migration, backup, correction, and notification plan:
Refund request / decision / execution evidence:
Support and maintenance costs:
Retirement conditions, existing commitments, customer data export, and retention:
Practice: practice/lifecycle-plan.json remains a draft. Adding a priority field in version 0.2 is proposed only. No migration, sale, support resolution, refund, or customer notification is recorded. practice/evaluation-plans.csv contains unexecuted real-environment checks.
Run the practice checks
From the extracted part-06/ directory:
python3 practice/verify_examples.py
This standard-library script checks the supplied funnel arithmetic, pricing and inventory calculations, prototype CSV structure, example-row rules, and expected invalid-row findings. It does not test customer demand, software import compatibility, usability, accessibility, AI performance, or a live store. Example-Verification.json records the executed file checks. Keep actual evaluation observations in practice/observations.csv when an evaluation is authorized and performed.