This hub consolidates enablement and onboarding strategies for the aswritten beta, centering on the tension between user-led discovery and structured separation. Guidance is anchored by [Tony's technical-user separation principle] (Position_TechnicalUserSeparationPrinciple) (Mar 17), which mandates that users initiate fresh projects to avoid conflict with existing repositories—a stance reinforced by [his specific implementation advice] (Obs_SeparationSolutionQuote). This focus on isolation emerged partly from [prospect feedback] (Position_TighterOnboarding) (Mar 11) requesting clearer distinctions between documentation and AI-driven workflows. The onboarding experience is further shaped by [five recurring user questions] (Position_FiveQuestionsEveryUserAsks) and [Scarlet's first-use framing] (Obs_ChatNotCodingSession), which encourages treating the tool as a conversational partner rather than a traditional coding environment. Underlying these tactical choices is a conceptual distinction: [human-led onboarding] (Narrative_OnboardingEffectivenessVsCoverage) (Mar 13) is framed as a method to increase knowledge coverage rather than inherent product effectiveness, with [live bootstrapping guidance] (Obs_BootstrappingGuidance) serving as a precursor to future automated onboarding modes.
Witness phrases
verbatim The best thing is to have a completely new thing that haven't started any repos for or anything and then don't let it touch anything else. Keep them separate.
verbatim Human onboarding increases knowledge coverage, not product effectiveness
verbatim The more involved people are, the more they need separation from their own chaos.
verbatim The necessity of manual onboarding is framed as an optimization phase, not a permanent requirement for product utility.
verbatim User demand for clearer documentation-vs-AI separation highlights a potential friction point in current self-serve onboarding.
In this area
Narrative_OnboardingEffectivenessVsCoverage Onboarding: Effectiveness vs. Coverage — A Key Distinction
ObservationObs_BootstrappingGuidance Scarlet's live onboarding guidance on what to ingest first — the content that should be automated in an onboarding mode.
ObservationObs_ChatNotCodingSession Scarlet's guidance on first-use framing: treat aswritten as a chat session, not a coding session.
ObservationObs_SeparationSolutionQuote Tony's prescribed solution for technical user adoption — start completely fresh, keep aswritten separate from existing repos.
3 further nodes are not published in the public projection. Each node links from the entity index.