Project
Check year crossings and invalid week 53, rejecting Boolean components and dates outside the calendar range.
WeekOrison gives calendar-boundary code a place in your Windows project conversation. Bring week-based inputs to a compatible model, then review the proposed conversion where the API meets stored dates.
from datetime import date
def iso_week_date(year, week, weekday):
values = (year, week, weekday)
if any(type(x) is not int for x in values):
raise ValueError("integer components")
if not 1 <= year <= 9999:
raise ValueError("year range")
if not 1 <= week <= 53 or not 1 <= weekday <= 7:
raise ValueError("week or weekday range")
return date.fromisocalendar(year, week, weekday)Check year crossings and invalid week 53, rejecting Boolean components and dates outside the calendar range.
Compare actual behavior with the expected result. If a check fails, investigate it before applying more changes.
Base URL, credentials and a reachable server.
from datetime import date
def iso_week_date(year, week, weekday):
values = (year, week, weekday)
if any(type(x) is not int for x in values):
raise ValueError("integer components")
if not 1 <= year <= 9999:
raise ValueError("year range")
if not 1 <= week <= 53 or not 1 <= weekday <= 7:
raise ValueError("week or weekday range")
return date.fromisocalendar(year, week, weekday)WeekOrison is a Windows AI coding workspace for changes where a calendar convention crosses an application boundary. Open the project and describe the date a user or API caller intends to identify. Ask the model to inspect input validation, conversion and storage together, so the proposed correction follows the full path of the value.
For example, request a review of ISO week-date input near a year boundary. Supply the week year, week and weekday alongside the calendar date you expect. Ask how the existing implementation handles that combination and invalid week numbers. The task is to align your application with its stated convention, rather than to infer one from a field label.
Read the proposed edits for changes to accepted inputs and error responses. A conversion may return the right date for an ordinary week while the interface still mislabels the year. Run relevant project tests across the boundary and inspect the stored value and displayed result before deciding that the correction is complete.
Choose an uncensored AI model when it is available through your supported OpenAI-compatible or Anthropic endpoint. Provide credentials if needed. Its restrictions, tools and context capacity depend on the model and server; the workspace gives you a place to examine suggestions against concrete dates and the code that handles them.
Do not assume that at a year boundary. Provide a known expected date for your week-based input and inspect how the application labels each component. A test should verify the converted date and the fields used to request it.
No. Validate the complete combination according to the convention your application uses. Ask the model to inspect the conversion library and caller error handling, then include both valid and invalid combinations in the checks for the proposed patch.
Later serialization or field mapping may change the value or label. Follow the converted result to the stored representation and back to the interface. This keeps a helper-level correction from hiding a separate mismatch elsewhere in the application.
Include input components, expected date and relevant runtime assumptions without real user records. Check tool destinations when executing it: a separately running local model server does not make every connected tool local or set its execution environment.
WeekOrison · Updated 2026-10-25