Project activity

Verified that AWS Cost Management is now returning the first cost-and-usage dataset and recorded the dated baseline privately. Billing figures, account details, and credentials are intentionally excluded from this public record.

Defined the smallest operator control workflow for one event, including explicit readiness checks, state changes, recovery rules, and an auditable history. This remains architecture only and has not been implemented.

Kept paid AWS services and media-resource automation outside the first control-plane design until current costs, operating assumptions, and shutdown behavior can be reviewed and approved.

Completed the private control-plane data and access contract, including safe state changes, immutable history, operator roles, authenticated sessions, retention boundaries, and separation from public project activity. Implementation has not started.

Authored and validated the source-only AWS control-plane foundation for retained event data, invite-only operator access, bounded usage, and an authorized API shell. Automated schema, policy, and AWS template checks passed; no application runtime or paid media service was deployed.

Completed an AWS review-only infrastructure preview for the control-plane foundation. AWS reported the proposed additions as available with no validation errors; the preview remains unexecuted and no resources were provisioned.

Deployed and read back the approved development control-plane foundation. Retained event storage, invite-only operator authentication, access roles, a route-free authorized API shell, throttling, and bounded logs are active. Application routes, processing code, operator accounts, and media services have not been created.

Implemented and validated the first source-only operator API slice for authenticated event reads and guarded state transitions, including role checks, explicit confirmations, atomic history, safe retries, bounded logs, and focused tests. The functions and routes have not been deployed.

Prepared private, versioned deployment artifacts and completed an AWS review-only preview of the first operator API slice. The preview passed validation and remains unexecuted; the live application is unchanged, with no processing functions or routes deployed.

Attempted the approved operator API deployment. AWS rejected the processing-function capacity settings and automatically restored the previous working foundation. Verified that no processing functions or application routes remain live, then prepared a corrected review boundary for the next approval.

Validated the corrected operator API configuration and completed a fresh AWS review-only preview. The proposed application additions remain unexecuted, and the live foundation still has no processing functions or application routes.

Deployed and verified the separately approved first operator API slice. Two authenticated routes and their processing functions are active with restricted permissions, bounded capacity, and limited log retention. Anonymous access is rejected; no operator account, event data, hosting application, or media service was created.

Defined the owner-controlled invitation and isolated development-test procedure for the first authenticated operator workflow. The directory and event store were verified empty; no identity, credential, token, operator data, event data, or media resource was created.

Created the first owner-approved, invite-only development operator account with the restricted Operator role. AWS delivered the temporary sign-in information directly to the operator; no credential or identity detail was added to the project record or public activity, and no event or media data was created.

Completed compatibility-safe project-site maintenance, including aligned framework and hosting-tool updates, security patches, and rendered-page checks. Remaining upstream dependency issues are tracked privately; no public deployment was performed as part of this work.

Deployed the approved AWS-hosted visitor, project-activity, private operator, and sign-in callback surfaces. The hosted routes and security headers passed direct checks; no media service or customer event data was created.

Added and verified isolated DNS records for the new public SML TV and private operator hostnames while leaving the Company's existing main website and service records unchanged. Both custom hosts and their intended routes are live over HTTPS with the approved security headers.

Established this activity page as the public, dated record of completed project work and approved decisions.

Helped establish the Company’s new AWS account as the owner-controlled home for future SML TV infrastructure and billing.

Created and verified a separate administrator identity for day-to-day project work so the Company’s root login is not required for normal operations.

Secured the administrator login with console access and multi-factor authentication, and confirmed that its administrative permissions are working.

Enabled and verified billing access for the administrator identity while keeping account ownership and payment responsibility with the Company.

Connected temporary command-line access to the verified Company AWS identity without storing long-lived access keys in the project.

Completed a read-only AWS account baseline. No existing streaming, application, database, storage, compute, or delivery resources were found in the two reviewed regions.

Activated AWS Cost Explorer. AWS is preparing the first cost-and-usage dataset, which may take up to 24 hours before it can be reviewed.

Added a sanitized AWS account baseline to the private project record and preserved it in the Company’s private source repository.

Defined the living project-page format: goals, milestones, decision summaries, open questions, next actions, and a public change log.

Established dated daily work records, permanent R&D and project-page tracks, and a weekly invoice workflow that uses only separately supplied hours.

Defined the proposed operator workflow as Draft → Scheduled → Preflight → Ready → Live → Completed. The operations backend remains a proposal and has not been implemented.

Outlined an operator-friendly dashboard that would hide routine AWS complexity while keeping major production, security, billing, and infrastructure decisions controlled by the Company.

Set Oregon as the primary AWS region for SML TV and confirmed that future development infrastructure will live in AWS rather than running as a local Mac-hosted environment.

Created and validated a reusable CloudFormation foundation with automated linting, AWS template validation, and a policy check that permits only standard configuration parameters.

Deployed the reviewed foundation and verified that it contains only five standard configuration parameters, with no compute, streaming, database, networking, or application-hosting services created.

Preserved the verified infrastructure template, policy checks, deployment record, and next actions in the Company’s private source repository.

AWS Cost Management is still preparing and propagating the first cost-and-usage dataset. Work will resume with that review before any paid service is approved or deployed.

Created the first public SML TV proposal in plain language for a broadcast and transmission audience.

Documented the proposed Company-owned product boundary: AWS would run managed infrastructure while the Company would own its customers, events, purchases, subscriptions, access rules, and viewer experience.

Added an original workflow illustration showing primary and backup contribution paths from production through cloud processing to viewers.

Added estimate-only cost scenarios, development terms, milestone expectations, Company-owned expense controls, and weekly Net 14 invoicing terms.

Published and visually checked the proposal, including the workflow artwork, AWS reference links, estimate language, and development section.

Standardized the public wording to use “the Client” and “the Company” and removed personal names from the proposal.