Why Harrington is built the way it is.

Authorship is not negotiable

When you write a song, you are the author. Not the tool you used, not the AI that suggested a line. A song that was written for you isn't yours — and most songwriters know the difference, even if they can't always articulate it.

Harrington is built to protect that. It does not generate songs. It does not rewrite sections. It does not make creative decisions on your behalf. What it does: analyze, suggest, and offer alternatives — and then get out of the way so you can decide.

This is a deliberate design choice, not a limitation. "Answers" would undermine your agency. By providing "options", Harrington keeps you in the driver's seat.

Appropriate tools protect authorship

Every AI action in Harrington returns options, not answers — but not every action belongs everywhere. Song-level tools like Song Coach and Theme Check help you understand the whole song. Section-level tools like Structural Guidance and Chord Progression help a verse, chorus, bridge, or other section do its job. Line-level tools like Spark, Suggest, Refine, and Rhyme help with the local craft decision in front of you.

The boundaries are part of the philosophy. Spark belongs on a line because it opens one local possibility. Spark at the section or song level would start to behave like a generator. Structural guidance belongs at the section level because it outlines a role, not a lyric. Theme analysis belongs at the song level because it reports what the whole draft appears to be saying. Harrington keeps those scales separate so the songwriter keeps making the creative decisions.

Evidence protects authorship

If Harrington is going to say "you stay the author", the product needs to help you defend that claim. The audit trail exists for that reason. It records the shape of the work: what you wrote, what the tool suggested, what you changed, what you kept, and when those decisions happened.

That record is not there to grade you or turn your process into surveillance theater. It is there so, if authorship is ever questioned, you have something better than vibes. You can show a trail of human choices. You can demonstrate that AI suggestions were inputs you reacted to, not a finished song you accepted wholesale.

The point is not to make creativity bureaucratic. The point is to make the author's role visible enough to protect.

Reports are for better human collaboration

The coaching report has a different purpose. It helps a coach, mentor, co-writer, producer, or worship director understand the current state of a song quickly: what the writer is trying to do, what changed, where the draft may be stuck, and what questions are worth discussing.

It is not a substitute for a coach. A report cannot know the writer's courage, taste, history, community, voice, or calling. It can only summarize the workbench evidence so two humans can get on the same page faster and spend the conversation on judgment, taste, and direction.

Your songs are yours — that is a trust statement

Song data is stored on Harrington's servers so your work persists across devices. When you use AI features, requests are sent to model providers. This is honest: Harrington is a web-based workbench, not a purely offline tool.

What that does not mean: Harrington does not use your songs to train models. Your songs are yours. You can export them in open formats at any time. You can delete your account and data. If your subscription lapses, you retain read-only access and can export before deciding what to do next.

That is the trust commitment: ownership, export, and deletion are in your hands — not locked behind the product.

The AI works only with what you tell it

When Harrington's AI features run, the context they receive is limited strictly to what you have explicitly and consciously provided: your songwriter profile — the personality, influences, experience, and preferences you described during onboarding — and the song or section you are actively working on. That is the complete box.

Harrington does not infer preferences from how you use the app, pull data from external sources, analyse your editing patterns, or research you in any way beyond what you have directly told us. We take your input at face value.

This has a practical consequence: the quality of the AI's help is a direct function of what you put in. A fuller, more honest songwriter profile produces more relevant suggestions. A minimal one produces generic ones. That is not a limitation — it is the design. You are in control of what the AI knows about you.

Harrington records detailed product activity for authorship audit trails, coach reports, debugging, safety, and product improvement. That activity record is not used as hidden personality profiling for the AI. AI context still comes from explicit song, profile, and workflow inputs, plus the specific report or audit artifact you choose to generate.

No feature cliffs

Every released feature in Harrington is available to every paid member. Solo and Pro differ in how much AI usage is included per month, not in what you can do. There are no craft tools locked behind a higher tier.

Pro members can opt into early access for features still in development through Harrington Labs — a settings area where upcoming features can be enabled individually, not all at once. Usage from Labs determines what ships to everyone. Features that prove themselves graduate to general availability for all paid members. Features that don't get used don't ship.

Pro also includes a higher AI allotment and a direct feedback channel. But the distinction between Solo and Pro is never about access to finished tools — it's about capacity and participation in what's being built.

Real workflow handoff

A song that can't leave the tool isn't useful. Harrington is designed around the idea that the writing environment should hand off cleanly to the production environment.

Export is first-class: native OnSong, documented ChordPro with flow metadata, PDF lyric and lead sheets, Word documents, and plain text. Character-exact chord alignment, section structure, flow cues, page layout, and Nashville numbers are part of the workbench because the song is not finished when the app looks good. It is finished when a singer, band, congregation, or collaborator can actually use it.

Human authorship requires a human

Harrington is designed for use by an individual human being making creative decisions. This is not incidental. It is the premise.

Using Harrington through an automated script, an AI agent, an orchestration tool, or any non-human interface — including tools like Claude Desktop or similar — is explicitly prohibited. Not because of a technical limitation, but because it is a categorical misuse of what the tool is for. If an agent is writing the song, there is no author and therefore the authorship promise is void.

Similarly, each account is for one person. Not one team, not one organization, not one shared account across employees. One human being, doing their own creative work.

These aren't arbitrary rules — they're the same principle stated two different ways. Authorship is personal. So is the account.

The legal specifics of how individual licensing works are in our Terms of Service.

A workbench, not a generator

The most important thing to understand about Harrington: it is a workbench. It gives you structured space to work, tools to analyze your work, and assistance when you're stuck. It does not build the thing for you.

That distinction is the foundation for trust — especially in communities where authorship matters. Worship leaders singing their congregation's songs. Songwriters whose work reflects their own experience. Mentors who want to teach craft, not shortcut it.

Harrington helps you write better songs — without writing them for you.