Boskeopolis is an obscure city-state in the Verdazul archipelago in the Pacific Ocean. It’s notable for its persistent violation o’ the laws o’ physics, biology, & economics ( tho, to be fair, real life doesn’t obey that last 1, either ). As such, any inconsistencies within these stories should be blamed on glitches, for I’m ’fraid the world o’ Boskeopolis Stories is still just in beta.

In that city lives a perfectionist thief named Autumn Springer, who, with her timid skeletal partner, Edgar Winters, & sometimes with his cheerful chemist friend, Dawn Summers, go on heists & explore wild lands for treasure. That is, when she isn’t mired in the various political, environmental, or personal calamities created by Boskeopolis’s other peculiar citizens; or isn’t dug into domestic concerns o’ work, errands, & her relationship with Edgar & Dawn; or isn’t burdened by her own chaotic mental state.

See the “Person’s Represented” section below for mo’ details ’bout the various neuroses o’ hers & many other Boskeopoleon citizens’.

Boskeopolis Stories is an experimental adventure/character-oriented short story series that plays round with many genres, moods, & tones, & e’en sometimes includes dynamic, randomized, or interactive elements using JavaScript. Also, its chronology isn’t straightforward, or e’en a single, consistent line. Don’t worry too much ’bout reading these stories in the right order — ’cept for maybe those with #’d parts, like the “DISTURBED” stories. Nor should one worry too much ’bout making sense out o’ every story; one shouldn’t have to perfectly understand a story the 1st time it’s read to enjoy it. As you read mo’ & mo’ stories, you’ll be able to piece together how they all fit, anyway.

On Story Titles & Codes

Just ’bout all story & bit titles are all-caps. Imagine them being yelled by a belligerent idiot. Don’t be too turned off by them: every story also has a shorter “code name” that can be found @ the end o’ the code string that starts with “#BOSK” & is usually just ’bove the title. These are much mo’ convenient to remember, & I recommend using these when referencing stories.

Every story also has a 6-character code in the middle o’ the “#BOSK” string for li’l logical reason, other than as perhaps a compact way to give misc info ’bout each story or a way to reference The Simpson’s silly episode codes. This code comprises 4 codes, the 2nd 2 comprising 2 characters each.

For those curious, here’s what each code means:

• The 1st code is an alphabetical letter that represents the season in which the story was published. A = 1, B = 2, etc.

• The 2nd code is also an alphabetical letter that represents the relative order in which the story was published within that season. For example, the “HURRY” story was the 5th story published in season 3, so its 2nd character is E.

• The 3rd code is the most vague. It’s a 2-character hexadecimal # that roughly represents that story’s absolute order in terms o’ when ’twas written, independent o’ publication. For instance, tho the “SHIP” story was the 1st published story, ’twas the 9th story written, so its code is 08 ( 1st value is 00, as in most hexidecimal bytes ). Attentive readers will notice holes in the sequence o’ hexidecimal #s, signifying rejected stories. For example, the 1st story I wrote, way back @ the end o’ 2011, was ne’er published ( for good reason — trust me ), so 00 is ne’er used.

  I say this code is vague ’cause these stories weren’t written 1 after the other, but written concurrently, starting & stopping @ varying times. The fact that I wasn’t consistent in when I chose to give a code to a story — when I started the 1st draft or when I finished — or how they’re portioned — the “DISTURBED” stories all have the same code, but the “GENIE” stories have different codes — makes this e’en mo’ imprecise.

• The 4th code is simply the story’s absolute publication order, also represented by a 2-character hexidecimal value. Read down the codes in the archives page & see that they rise consistently from 00.