Camelot Software Planning
Japanese video game developer
Camelot Co., Ltd. (doing business as Camelot! Software Planning) is a Japanese video game development company established in 1994 and headquartered in Shinjuku, Tokyo. It is known for developing sports games, particularly within Nintendo's Mario franchise, as well as the RPG series Golden Sun.
History
Camelot was founded on April 4, 1994 by Shugo Takahashi, the brother of producer Hiroyuki Takahashi, with the intention of developing games for Sony's PlayStation. They developed their first game, Beyond the Beyond, while providing assistance to Sonic! Software Planning on Shining Wisdom. They would then provide assistance on Sonic's next game, Shining the Holy Ark.
In April 1998, after Sega merged its investment in Sonic into its subsidiary Nextech, Hiroyuki Takahashi joined Camelot as its president. Camelot then finished development of Shining Force III in Sonic's place and moved on to develop titles for Nintendo consoles.
Begin with the source’s own compact description: “Camelot Software Planning” is japanese video game developer. The dossier treats that line as a proposition to test through Camelot, Software and Planning, not as a finished interpretation.
Why this record matters
The phrase “japanese video game developer” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.
Named sources, stable identifiers and responsible institutions provide the strongest route from overview to verifiable evidence. The source revision retrieved here is dated Aug 17, 2026. The linked authority identifier is Q684780. VIAF identifies the subject as 128097036. 3 of 3 selected statements include explicit references; 1 carry qualifiers and 0 use preferred rank. The first chronological checks are 1994 and 1998.
A concise general-reference account can conceal disagreements about scope, terminology or the weight assigned to individual sources. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Camelot Software Planning”, its source revision and the description used here.
- Expand the search: follow Camelot Software Planning primary sources, Camelot Software Planning archive and Camelot research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Camelot Software Planning”?
- Which cited source is closest to the event, object or claim?
- What terminology or title could unlock a more precise catalogue search?
Search terms from this dossier
This entry incorporates text from “Camelot Software Planning” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.