Template:MuGlobe/genre - Revision history

Edb: Add three canonical recording curation fields

2026-10-22T02:36:22Z

Add three canonical recording curation fields

muglobe-definition
← Older revision		Revision as of 02:36, 22 October 2026
Line 4:		Line 4:

	Published instructions and table fields are retained in the native protected definition. The latest October19 catalogue policy supersedes the former ten-year exclusion and introductory-sample limit.		Published instructions and table fields are retained in the native protected definition. The latest October19 catalogue policy supersedes the former ten-year exclusion and introductory-sample limit.

			== Recording curation fields ==
			All media rows use sixteen columns, ending with '''MuGlobe favorite''', '''Current hit''' and '''Authentic'''. Each cell contains a canonical <nowiki><muglobe-flag video="VIDEO_ID" field="muglobeFavorite" /></nowiki> tag (use field currentHit and authentic for the next cells). Click the displayed value to edit through [[Special:RecordingCuration]]. Only superadministrators can save these independent, global recording flags. New recordings default false; never infer editorial approval from metadata. Native curation revisions are authoritative and project to the playback database.
Line 2:		Line 2:
	"id": "genre",		"id": "genre",
	"label": "Genre",		"label": "Genre",
	"version": 13,		"version": 14,
	"published": true,		"published": true,
	"sections": [		"sections": [
Line 60:		Line 60:
	"requireContent": true,		"requireContent": true,
	"allowSubsections": true,		"allowSubsections": true,
	"starter": "Build a comprehensive catalogue for all-day listening. Aim for at least20 good distinct recordings per genre;20 is a floor, not a cap. Prioritize discovering recent music and retain worthwhile older music as playable content. Age alone is not a rejection. Verify each specific musical performance and community, preserve truthful original-release, performance and upload dates separately, and keep unknown dates unknown. Use artist, work, native-language, channel, playlist, institution and broadcaster discovery before declaring a shortage. Check duplicates and one actual advancing embed per new accepted video. Avoid repeated uploads of one work, instructional/nonmusical material and adjacent but nonconforming recordings. Preserve good existing material and local recording scopes.\n\nThe listening profile describes how this genre is used. Repertoire is popular, traditional or classical. Field use is regional or context-only: broad umbrella/uncorroborated fields are contextual evidence and cannot establish local dominance. Explain this judgment in Notes. Neither field is an audience measurement.\n\n{\| class=\"wikitable\"\n\|+ MuGlobe listening profile\n! Repertoire !! Field use !! Notes\n\|}\n\nEach track has its own Repertoire kind (popular, traditional or classical); a genre may contain more than one. Dates preserve known precision: YYYY-MM-DD, YYYY-MM or YYYY; a documented bounded interval uses start/end, such as 2017/2019. The entire known interval must qualify for recent listening. Enter unknown otherwise. Format is audio, music-video, live or unknown. Opening is prompt, delayed or unknown; record actual evidence, never infer a prompt start solely from the format. Places use semicolon-separated country:Name or region:ID keys supported by the musical scene, not nationality or concert location alone. Fit is supported, pending or rejected. Evidence contains supporting HTTPS links; Review note explains what those sources establish and any limits. Supported means the specific recording was reviewed; oEmbed alone is insufficient. Add native footnotes in Notes for readers. The explicit compiler retains exact native revisions; ordinary builds never author content. Historical/undated examples remain available for listening with truthful descriptive metadata.\n\n{\| class=\"wikitable muglobe-performances\"\n\|+ MuGlobe representative performances\n! Artist !! Performance / song / title !! Embedded player URL !! Notes !! Repertoire kind !! Repertoire date !! Recording date !! Format !! Opening !! Places !! Fit !! Evidence !! Review note\n\|}"		"starter": "Build a comprehensive catalogue for all-day listening. Aim for at least20 good distinct recordings per genre;20 is a floor, not a cap. Prioritize discovering recent music and retain worthwhile older music as playable content. Age alone is not a rejection. Verify each specific musical performance and community, preserve truthful original-release, performance and upload dates separately, and keep unknown dates unknown. Use artist, work, native-language, channel, playlist, institution and broadcaster discovery before declaring a shortage. Check duplicates and one actual advancing embed per new accepted video. Avoid repeated uploads of one work, instructional/nonmusical material and adjacent but nonconforming recordings. Preserve good existing material and local recording scopes.\n\nThe listening profile describes how this genre is used. Repertoire is popular, traditional or classical. Field use is regional or context-only: broad umbrella/uncorroborated fields are contextual evidence and cannot establish local dominance. Explain this judgment in Notes. Neither field is an audience measurement.\n\n{\| class=\"wikitable\"\n\|+ MuGlobe listening profile\n! Repertoire !! Field use !! Notes\n\|}\n\nEach track has its own Repertoire kind (popular, traditional or classical); a genre may contain more than one. Dates preserve known precision: YYYY-MM-DD, YYYY-MM or YYYY; a documented bounded interval uses start/end, such as 2017/2019. The entire known interval must qualify for recent listening. Enter unknown otherwise. Format is audio, music-video, live or unknown. Opening is prompt, delayed or unknown; record actual evidence, never infer a prompt start solely from the format. Places use semicolon-separated country:Name or region:ID keys supported by the musical scene, not nationality or concert location alone. Fit is supported, pending or rejected. Evidence contains supporting HTTPS links; Review note explains what those sources establish and any limits. Supported means the specific recording was reviewed; oEmbed alone is insufficient. Add native footnotes in Notes for readers. The explicit compiler retains exact native revisions; ordinary builds never author content. Historical/undated examples remain available for listening with truthful descriptive metadata.\n\n{\| class=\"wikitable muglobe-performances\"\n\|+ MuGlobe representative performances\n! Artist !! Performance / song / title !! Embedded player URL !! Notes !! Repertoire kind !! Repertoire date !! Recording date !! Format !! Opening !! Places !! Fit !! Evidence !! Review note !! MuGlobe favorite !! Current hit !! Authentic\n\|} Every recording row has sixteen columns, ending with MuGlobe favorite, Current hit and Authentic. Use canonical \u003Cmuglobe-flag video=\"VIDEO_ID\" field=\"muglobeFavorite\" /\u003E, currentHit and authentic tags. These independent global booleans default false; only the superadministrator changes them through Recording curation. Duplicate video IDs share flags. Preserve original music, evidence and start offsets."
	},		},
	{		{

Edb: Adopt Ed’s comprehensive catalogue policy: at least20 good recordings, recent priority, worthwhile older content retained and playable.

2026-10-19T13:12:35Z

Adopt Ed’s comprehensive catalogue policy: at least20 good recordings, recent priority, worthwhile older content retained and playable.

@@ Line 1: / Line 1: @@
-This is the published first-pass outline for '''Genre''' articles on MuGlobe.com, extrapolated from Ed's Country template at his request on October 17, 2026.
+Genre article outline and catalogue policy.
-Required sections must contain substantive text. Optional sections may be omitted; when included they must contain substantive text. Keep sections in the listed order. Subheadings are allowed within each section. Cite sources and use representative musical examples where available.
+Build a comprehensive catalogue for all-day listening. Aim for at least20 good distinct recordings per genre;20 is a floor, not a cap. Prioritize discovering recent music and retain worthwhile older music as playable content. Age alone is not a rejection. Verify each specific musical performance and community, preserve truthful original-release, performance and upload dates separately, and keep unknown dates unknown. Use artist, work, native-language, channel, playlist, institution and broadcaster discovery before declaring a shortage. Check duplicates and one actual advancing embed per new accepted video. Avoid repeated uploads of one work, instructional/nonmusical material and adjacent but nonconforming recordings. Preserve good existing material and local recording scopes.
-* '''Summary:''' Introduce the genre and its recognizable musical identity.
+Published instructions and table fields are retained in the native protected definition. The latest October19 catalogue policy supersedes the former ten-year exclusion and introductory-sample limit.
@@ Line 2: / Line 2: @@
 	"id": "genre",
 	"label": "Genre",
-	"version": 12,
+	"version": 13,
 	"published": true,
 	"sections": [
@@ Line 60: / Line 60: @@
 			"requireContent": true,
 			"allowSubsections": true,
-			"starter": "Curate 1–10 specific recordings with artist, title, canonical YouTube embed URL and notes. Verify the exact recording's musical identity and local scene, not only its artist or URL metadata. Keep useful historical and live examples. For default listening, use the last ten years: popular repertoire qualifies by its supported original release date, even when studio sessions occurred earlier; traditional/classical repertoire may be older but its particular recording or performance must qualify. Preserve actual recording dates separately, including unknown dates. Uploads, remasters, compilations and later live versions do not reset the original popular repertoire date. Unknown dates remain unknown. Prefer a suitable prompt-start studio/official recording first; good live performances belong later in the playlist and must not be deleted simply for being live.\n\nThe listening profile describes how this genre is used. Repertoire is popular, traditional or classical. Field use is regional or context-only: broad umbrella/uncorroborated fields are contextual evidence and cannot establish local dominance. Explain this judgment in Notes. Neither field is an audience measurement.\n\n{| class=\"wikitable\"\n|+ MuGlobe listening profile\n! Repertoire !! Field use !! Notes\n|}\n\nEach track has its own Repertoire kind (popular, traditional or classical); a genre may contain more than one. Dates preserve known precision: YYYY-MM-DD, YYYY-MM or YYYY; a documented bounded interval uses start/end, such as 2017/2019. The entire known interval must qualify for recent listening. Enter unknown otherwise. Format is audio, music-video, live or unknown. Opening is prompt, delayed or unknown; record actual evidence, never infer a prompt start solely from the format. Places use semicolon-separated country:Name or region:ID keys supported by the musical scene, not nationality or concert location alone. Fit is supported, pending or rejected. Evidence contains supporting HTTPS links; Review note explains what those sources establish and any limits. Supported means the specific recording was reviewed; oEmbed alone is insufficient. Add native footnotes in Notes for readers. The explicit compiler retains exact native revisions; ordinary builds never author content. Historical/undated examples remain separate from automatic contemporary listening.\n\n{| class=\"wikitable muglobe-performances\"\n|+ MuGlobe representative performances\n! Artist !! Performance / song / title !! Embedded player URL !! Notes !! Repertoire kind !! Repertoire date !! Recording date !! Format !! Opening !! Places !! Fit !! Evidence !! Review note\n|}"
+			"starter": "Build a comprehensive catalogue for all-day listening. Aim for at least20 good distinct recordings per genre;20 is a floor, not a cap. Prioritize discovering recent music and retain worthwhile older music as playable content. Age alone is not a rejection. Verify each specific musical performance and community, preserve truthful original-release, performance and upload dates separately, and keep unknown dates unknown. Use artist, work, native-language, channel, playlist, institution and broadcaster discovery before declaring a shortage. Check duplicates and one actual advancing embed per new accepted video. Avoid repeated uploads of one work, instructional/nonmusical material and adjacent but nonconforming recordings. Preserve good existing material and local recording scopes.\n\nThe listening profile describes how this genre is used. Repertoire is popular, traditional or classical. Field use is regional or context-only: broad umbrella/uncorroborated fields are contextual evidence and cannot establish local dominance. Explain this judgment in Notes. Neither field is an audience measurement.\n\n{| class=\"wikitable\"\n|+ MuGlobe listening profile\n! Repertoire !! Field use !! Notes\n|}\n\nEach track has its own Repertoire kind (popular, traditional or classical); a genre may contain more than one. Dates preserve known precision: YYYY-MM-DD, YYYY-MM or YYYY; a documented bounded interval uses start/end, such as 2017/2019. The entire known interval must qualify for recent listening. Enter unknown otherwise. Format is audio, music-video, live or unknown. Opening is prompt, delayed or unknown; record actual evidence, never infer a prompt start solely from the format. Places use semicolon-separated country:Name or region:ID keys supported by the musical scene, not nationality or concert location alone. Fit is supported, pending or rejected. Evidence contains supporting HTTPS links; Review note explains what those sources establish and any limits. Supported means the specific recording was reviewed; oEmbed alone is insufficient. Add native footnotes in Notes for readers. The explicit compiler retains exact native revisions; ordinary builds never author content. Historical/undated examples remain available for listening with truthful descriptive metadata.\n\n{| class=\"wikitable muglobe-performances\"\n|+ MuGlobe representative performances\n! Artist !! Performance / song / title !! Embedded player URL !! Notes !! Repertoire kind !! Repertoire date !! Recording date !! Format !! Opening !! Places !! Fit !! Evidence !! Review note\n|}"
 		},
+		{
@@ Line 80: / Line 80: @@
+		}
 	],
-	"instructions": "Explain what listeners will hear, where the genre developed and where it is now adopted. Separate present-day listening from origins, and describe specific places and communities rather than assuming uniform national popularity. A historical genre may have limited present activity. Related genres is optional. Use sources and accessible musical examples. Hotspot mushrooms is the final section. Understand the connected musical landscape before choosing circles. Use nearby cities as clues to a wider region, not automatic isolated mushrooms. Include intervening countryside, distinguish meaningful detached scenes, and calibrate the fading field across the whole heartland. Centers need not be cities. Use the fewest useful broad fields, with concise Notes explaining editorial judgment. No source column or per-mushroom citation is required. Manual coordinates and explicit compilation remain in use. Representative recordings follow the current listening editorial policy: verify the specific arrangement and local scene; record original repertoire and recording dates separately; contemporary default listening uses a rolling ten-year window. Keep historical examples separately and preserve good live recordings, sequencing a suitable prompt-start studio/official recording first. Use the required listening-profile and performance tables, with evidence and explicit uncertainty. Do not treat upload/reissue dates as recording dates or oEmbed metadata as musical proof."
+	"instructions": "Build a comprehensive catalogue for all-day listening. Aim for at least20 good distinct recordings per genre;20 is a floor, not a cap. Prioritize discovering recent music and retain worthwhile older music as playable content. Age alone is not a rejection. Verify each specific musical performance and community, preserve truthful original-release, performance and upload dates separately, and keep unknown dates unknown. Use artist, work, native-language, channel, playlist, institution and broadcaster discovery before declaring a shortage. Check duplicates and one actual advancing embed per new accepted video. Avoid repeated uploads of one work, instructional/nonmusical material and adjacent but nonconforming recordings. Preserve good existing material and local recording scopes. Explain what listeners will hear, where the genre developed and where it is now adopted. Separate present-day listening from origins, and describe specific places and communities rather than assuming uniform national popularity. A historical genre may have limited present activity. Related genres is optional. Use sources and accessible musical examples. Hotspot mushrooms is the final section. Understand the connected musical landscape before choosing circles. Use nearby cities as clues to a wider region, not automatic isolated mushrooms. Include intervening countryside, distinguish meaningful detached scenes, and calibrate the fading field across the whole heartland. Centers need not be cities. Use the fewest useful broad fields, with concise Notes explaining editorial judgment. No source column or per-mushroom citation is required. Manual coordinates and explicit compilation remain in use.  Representative recordings use the required listening-profile and thirteen-column performance tables, with evidence and explicit uncertainty. Historical is descriptive age information, not an exclusion from listening. Keep native revisions authoritative and compilation deliberate."
+}

Edb: Preserve documented recording date intervals without inventing a session year

2026-10-18T19:35:33Z

Preserve documented recording date intervals without inventing a session year

muglobe-definition
← Older revision		Revision as of 19:35, 18 October 2026
Line 29:		Line 29:
	\|}		\|}

	Each track has its own Repertoire kind (popular, traditional or classical); a genre may contain more than one. Dates preserve known precision: YYYY-MM-DD, YYYY-MM or YYYY; ~~enter~~ unknown otherwise. Format is audio, music-video, live or unknown. Opening is prompt, delayed or unknown; record actual evidence, never infer a prompt start solely from the format. Places use semicolon-separated country:Name or region:ID keys supported by the musical scene, not nationality or concert location alone. Fit is supported, pending or rejected. Evidence contains supporting HTTPS links; Review note explains what those sources establish and any limits. Supported means the specific recording was reviewed; oEmbed alone is insufficient. Add native footnotes in Notes for readers. The explicit compiler retains exact native revisions; ordinary builds never author content. Historical/undated examples remain separate from automatic contemporary listening.		Each track has its own Repertoire kind (popular, traditional or classical); a genre may contain more than one. Dates preserve known precision: YYYY-MM-DD, YYYY-MM or YYYY; a documented bounded interval uses start/end, such as 2017/2019. The entire known interval must qualify for recent listening. Enter unknown otherwise. Format is audio, music-video, live or unknown. Opening is prompt, delayed or unknown; record actual evidence, never infer a prompt start solely from the format. Places use semicolon-separated country:Name or region:ID keys supported by the musical scene, not nationality or concert location alone. Fit is supported, pending or rejected. Evidence contains supporting HTTPS links; Review note explains what those sources establish and any limits. Supported means the specific recording was reviewed; oEmbed alone is insufficient. Add native footnotes in Notes for readers. The explicit compiler retains exact native revisions; ordinary builds never author content. Historical/undated examples remain separate from automatic contemporary listening.

	{\| class="wikitable muglobe-performances"		{\| class="wikitable muglobe-performances"
Line 2:		Line 2:
	"id": "genre",		"id": "genre",
	"label": "Genre",		"label": "Genre",
	"version": 11,		"version": 12,
	"published": true,		"published": true,
	"sections": [		"sections": [
Line 60:		Line 60:
	"requireContent": true,		"requireContent": true,
	"allowSubsections": true,		"allowSubsections": true,
	"starter": "Curate 1–10 specific recordings with artist, title, canonical YouTube embed URL and notes. Verify the exact recording's musical identity and local scene, not only its artist or URL metadata. Keep useful historical and live examples. For default listening, use the last ten years: popular repertoire qualifies by its supported original release date, even when studio sessions occurred earlier; traditional/classical repertoire may be older but its particular recording or performance must qualify. Preserve actual recording dates separately, including unknown dates. Uploads, remasters, compilations and later live versions do not reset the original popular repertoire date. Unknown dates remain unknown. Prefer a suitable prompt-start studio/official recording first; good live performances belong later in the playlist and must not be deleted simply for being live.\n\nThe listening profile describes how this genre is used. Repertoire is popular, traditional or classical. Field use is regional or context-only: broad umbrella/uncorroborated fields are contextual evidence and cannot establish local dominance. Explain this judgment in Notes. Neither field is an audience measurement.\n\n{\| class=\"wikitable\"\n\|+ MuGlobe listening profile\n! Repertoire !! Field use !! Notes\n\|}\n\nEach track has its own Repertoire kind (popular, traditional or classical); a genre may contain more than one. Dates preserve known precision: YYYY-MM-DD, YYYY-MM or YYYY; ~~enter~~ unknown otherwise. Format is audio, music-video, live or unknown. Opening is prompt, delayed or unknown; record actual evidence, never infer a prompt start solely from the format. Places use semicolon-separated country:Name or region:ID keys supported by the musical scene, not nationality or concert location alone. Fit is supported, pending or rejected. Evidence contains supporting HTTPS links; Review note explains what those sources establish and any limits. Supported means the specific recording was reviewed; oEmbed alone is insufficient. Add native footnotes in Notes for readers. The explicit compiler retains exact native revisions; ordinary builds never author content. Historical/undated examples remain separate from automatic contemporary listening.\n\n{\| class=\"wikitable muglobe-performances\"\n\|+ MuGlobe representative performances\n! Artist !! Performance / song / title !! Embedded player URL !! Notes !! Repertoire kind !! Repertoire date !! Recording date !! Format !! Opening !! Places !! Fit !! Evidence !! Review note\n\|}"		"starter": "Curate 1–10 specific recordings with artist, title, canonical YouTube embed URL and notes. Verify the exact recording's musical identity and local scene, not only its artist or URL metadata. Keep useful historical and live examples. For default listening, use the last ten years: popular repertoire qualifies by its supported original release date, even when studio sessions occurred earlier; traditional/classical repertoire may be older but its particular recording or performance must qualify. Preserve actual recording dates separately, including unknown dates. Uploads, remasters, compilations and later live versions do not reset the original popular repertoire date. Unknown dates remain unknown. Prefer a suitable prompt-start studio/official recording first; good live performances belong later in the playlist and must not be deleted simply for being live.\n\nThe listening profile describes how this genre is used. Repertoire is popular, traditional or classical. Field use is regional or context-only: broad umbrella/uncorroborated fields are contextual evidence and cannot establish local dominance. Explain this judgment in Notes. Neither field is an audience measurement.\n\n{\| class=\"wikitable\"\n\|+ MuGlobe listening profile\n! Repertoire !! Field use !! Notes\n\|}\n\nEach track has its own Repertoire kind (popular, traditional or classical); a genre may contain more than one. Dates preserve known precision: YYYY-MM-DD, YYYY-MM or YYYY; a documented bounded interval uses start/end, such as 2017/2019. The entire known interval must qualify for recent listening. Enter unknown otherwise. Format is audio, music-video, live or unknown. Opening is prompt, delayed or unknown; record actual evidence, never infer a prompt start solely from the format. Places use semicolon-separated country:Name or region:ID keys supported by the musical scene, not nationality or concert location alone. Fit is supported, pending or rejected. Evidence contains supporting HTTPS links; Review note explains what those sources establish and any limits. Supported means the specific recording was reviewed; oEmbed alone is insufficient. Add native footnotes in Notes for readers. The explicit compiler retains exact native revisions; ordinary builds never author content. Historical/undated examples remain separate from automatic contemporary listening.\n\n{\| class=\"wikitable muglobe-performances\"\n\|+ MuGlobe representative performances\n! Artist !! Performance / song / title !! Embedded player URL !! Notes !! Repertoire kind !! Repertoire date !! Recording date !! Format !! Opening !! Places !! Fit !! Evidence !! Review note\n\|}"
	},		},
	{		{

Edb: Clarify original popular release versus studio-session dates; preserve the ten-year rule and live sequencing

2026-10-18T19:34:05Z

Clarify original popular release versus studio-session dates; preserve the ten-year rule and live sequencing

muglobe-definition
← Older revision		Revision as of 19:34, 18 October 2026
Line 20:		Line 20:

	== Listening correction — October 18, 2026 ==		== Listening correction — October 18, 2026 ==
	Curate 1–10 specific recordings with artist, title, canonical YouTube embed URL and notes. Verify the exact recording's musical identity and local scene, not only its artist or URL metadata. Keep useful historical and live examples. For default listening, use the last ten years: popular ~~music needs both recent~~ original ~~repertoire and recent recording~~; traditional/classical repertoire may be older but its recording must qualify. Uploads, remasters, compilations and later live versions do not reset the original popular repertoire date. Unknown dates remain unknown. Prefer a suitable prompt-start studio/official recording first; good live performances belong later in the playlist and must not be deleted simply for being live.		Curate 1–10 specific recordings with artist, title, canonical YouTube embed URL and notes. Verify the exact recording's musical identity and local scene, not only its artist or URL metadata. Keep useful historical and live examples. For default listening, use the last ten years: popular repertoire qualifies by its supported original release date, even when studio sessions occurred earlier; traditional/classical repertoire may be older but its particular recording or performance must qualify. Preserve actual recording dates separately, including unknown dates. Uploads, remasters, compilations and later live versions do not reset the original popular repertoire date. Unknown dates remain unknown. Prefer a suitable prompt-start studio/official recording first; good live performances belong later in the playlist and must not be deleted simply for being live.

	The listening profile describes how this genre is used. Repertoire is popular, traditional or classical. Field use is regional or context-only: broad umbrella/uncorroborated fields are contextual evidence and cannot establish local dominance. Explain this judgment in Notes. Neither field is an audience measurement.		The listening profile describes how this genre is used. Repertoire is popular, traditional or classical. Field use is regional or context-only: broad umbrella/uncorroborated fields are contextual evidence and cannot establish local dominance. Explain this judgment in Notes. Neither field is an audience measurement.
Line 2:		Line 2:
	"id": "genre",		"id": "genre",
	"label": "Genre",		"label": "Genre",
	"version": 10,		"version": 11,
	"published": true,		"published": true,
	"sections": [		"sections": [
Line 60:		Line 60:
	"requireContent": true,		"requireContent": true,
	"allowSubsections": true,		"allowSubsections": true,
	"starter": "Curate 1–10 specific recordings with artist, title, canonical YouTube embed URL and notes. Verify the exact recording's musical identity and local scene, not only its artist or URL metadata. Keep useful historical and live examples. For default listening, use the last ten years: popular ~~music needs both recent~~ original ~~repertoire and recent recording~~; traditional/classical repertoire may be older but its recording must qualify. Uploads, remasters, compilations and later live versions do not reset the original popular repertoire date. Unknown dates remain unknown. Prefer a suitable prompt-start studio/official recording first; good live performances belong later in the playlist and must not be deleted simply for being live.\n\nThe listening profile describes how this genre is used. Repertoire is popular, traditional or classical. Field use is regional or context-only: broad umbrella/uncorroborated fields are contextual evidence and cannot establish local dominance. Explain this judgment in Notes. Neither field is an audience measurement.\n\n{\| class=\"wikitable\"\n\|+ MuGlobe listening profile\n! Repertoire !! Field use !! Notes\n\|}\n\nEach track has its own Repertoire kind (popular, traditional or classical); a genre may contain more than one. Dates preserve known precision: YYYY-MM-DD, YYYY-MM or YYYY; enter unknown otherwise. Format is audio, music-video, live or unknown. Opening is prompt, delayed or unknown; record actual evidence, never infer a prompt start solely from the format. Places use semicolon-separated country:Name or region:ID keys supported by the musical scene, not nationality or concert location alone. Fit is supported, pending or rejected. Evidence contains supporting HTTPS links; Review note explains what those sources establish and any limits. Supported means the specific recording was reviewed; oEmbed alone is insufficient. Add native footnotes in Notes for readers. The explicit compiler retains exact native revisions; ordinary builds never author content. Historical/undated examples remain separate from automatic contemporary listening.\n\n{\| class=\"wikitable muglobe-performances\"\n\|+ MuGlobe representative performances\n! Artist !! Performance / song / title !! Embedded player URL !! Notes !! Repertoire kind !! Repertoire date !! Recording date !! Format !! Opening !! Places !! Fit !! Evidence !! Review note\n\|}"		"starter": "Curate 1–10 specific recordings with artist, title, canonical YouTube embed URL and notes. Verify the exact recording's musical identity and local scene, not only its artist or URL metadata. Keep useful historical and live examples. For default listening, use the last ten years: popular repertoire qualifies by its supported original release date, even when studio sessions occurred earlier; traditional/classical repertoire may be older but its particular recording or performance must qualify. Preserve actual recording dates separately, including unknown dates. Uploads, remasters, compilations and later live versions do not reset the original popular repertoire date. Unknown dates remain unknown. Prefer a suitable prompt-start studio/official recording first; good live performances belong later in the playlist and must not be deleted simply for being live.\n\nThe listening profile describes how this genre is used. Repertoire is popular, traditional or classical. Field use is regional or context-only: broad umbrella/uncorroborated fields are contextual evidence and cannot establish local dominance. Explain this judgment in Notes. Neither field is an audience measurement.\n\n{\| class=\"wikitable\"\n\|+ MuGlobe listening profile\n! Repertoire !! Field use !! Notes\n\|}\n\nEach track has its own Repertoire kind (popular, traditional or classical); a genre may contain more than one. Dates preserve known precision: YYYY-MM-DD, YYYY-MM or YYYY; enter unknown otherwise. Format is audio, music-video, live or unknown. Opening is prompt, delayed or unknown; record actual evidence, never infer a prompt start solely from the format. Places use semicolon-separated country:Name or region:ID keys supported by the musical scene, not nationality or concert location alone. Fit is supported, pending or rejected. Evidence contains supporting HTTPS links; Review note explains what those sources establish and any limits. Supported means the specific recording was reviewed; oEmbed alone is insufficient. Add native footnotes in Notes for readers. The explicit compiler retains exact native revisions; ordinary builds never author content. Historical/undated examples remain separate from automatic contemporary listening.\n\n{\| class=\"wikitable muglobe-performances\"\n\|+ MuGlobe representative performances\n! Artist !! Performance / song / title !! Embedded player URL !! Notes !! Repertoire kind !! Repertoire date !! Recording date !! Format !! Opening !! Places !! Fit !! Evidence !! Review note\n\|}"
	},		},
	{		{

Edb: Add recording-level dates, local context, review evidence and prompt-start sequencing; preserve historical and live examples

2026-10-18T19:19:58Z

Add recording-level dates, local context, review evidence and prompt-start sequencing; preserve historical and live examples

muglobe-definition
← Older revision		Revision as of 19:19, 18 October 2026
Line 18:		Line 18:

	Representative performances supplies the editable genre playlist. Each row contains artist, title, canonical YouTube embedded player URL and explanatory notes. Native citations document the recording and its relevance. Explicit compilation publishes validated entries to the globe; ordinary edits never regenerate map assets.		Representative performances supplies the editable genre playlist. Each row contains artist, title, canonical YouTube embedded player URL and explanatory notes. Native citations document the recording and its relevance. Explicit compilation publishes validated entries to the globe; ordinary edits never regenerate map assets.

			== Listening correction — October 18, 2026 ==
			Curate 1–10 specific recordings with artist, title, canonical YouTube embed URL and notes. Verify the exact recording's musical identity and local scene, not only its artist or URL metadata. Keep useful historical and live examples. For default listening, use the last ten years: popular music needs both recent original repertoire and recent recording; traditional/classical repertoire may be older but its recording must qualify. Uploads, remasters, compilations and later live versions do not reset the original popular repertoire date. Unknown dates remain unknown. Prefer a suitable prompt-start studio/official recording first; good live performances belong later in the playlist and must not be deleted simply for being live.

			The listening profile describes how this genre is used. Repertoire is popular, traditional or classical. Field use is regional or context-only: broad umbrella/uncorroborated fields are contextual evidence and cannot establish local dominance. Explain this judgment in Notes. Neither field is an audience measurement.

			{\| class="wikitable"
			\|+ MuGlobe listening profile
			! Repertoire !! Field use !! Notes
			\|}

			Each track has its own Repertoire kind (popular, traditional or classical); a genre may contain more than one. Dates preserve known precision: YYYY-MM-DD, YYYY-MM or YYYY; enter unknown otherwise. Format is audio, music-video, live or unknown. Opening is prompt, delayed or unknown; record actual evidence, never infer a prompt start solely from the format. Places use semicolon-separated country:Name or region:ID keys supported by the musical scene, not nationality or concert location alone. Fit is supported, pending or rejected. Evidence contains supporting HTTPS links; Review note explains what those sources establish and any limits. Supported means the specific recording was reviewed; oEmbed alone is insufficient. Add native footnotes in Notes for readers. The explicit compiler retains exact native revisions; ordinary builds never author content. Historical/undated examples remain separate from automatic contemporary listening.

			{\| class="wikitable muglobe-performances"
			\|+ MuGlobe representative performances
			! Artist !! Performance / song / title !! Embedded player URL !! Notes !! Repertoire kind !! Repertoire date !! Recording date !! Format !! Opening !! Places !! Fit !! Evidence !! Review note
			\|}
Line 2:		Line 2:
	"id": "genre",		"id": "genre",
	"label": "Genre",		"label": "Genre",
	"version": 9,		"version": 10,
	"published": true,		"published": true,
	"sections": [		"sections": [
Line 60:		Line 60:
	"requireContent": true,		"requireContent": true,
	"allowSubsections": true,		"allowSubsections": true,
	"starter": "Curate 1–10 ~~representative~~ recordings, ~~preferably from official artists~~, ~~ensembles~~, ~~broadcasters, archives~~ or ~~cultural institutions~~. ~~Include living practice and~~ useful historical examples ~~where appropriate~~. ~~Credit~~ the ~~actual performers~~; ~~explain what to listen for~~ and ~~identify adaptations, excerpts or mixed~~-~~genre concerts. A~~ studio recording ~~or official music video is acceptable. Do~~ not ~~substitute search-result or playlist URLs~~ for ~~a specific performance~~.\n\~~nUse the four columns below~~. ~~Embedded player URL must be a complete canonical HTTPS YouTube embed URL~~, ~~for example https~~:/~~/www~~.~~youtube~~.~~com/embed/VIDEO_ID~~ (~~replace VIDEO_ID with~~ the ~~real 11~~-~~character identifier)~~. ~~Do not paste iframe HTML~~ or ~~URL parameters~~. Add ~~reliable~~ native ~~citations~~ in Notes ~~and include their reference list in the article~~. ~~Keep rows in the preferred listening order. Wiki publication stores these entries; the~~ explicit ~~performance~~ compiler ~~validates them and publishes the globe playlist~~.\n\n{\| class=\"wikitable muglobe-performances\"\n\|+ MuGlobe representative performances\n! Artist !! Performance / song / title !! Embedded player URL !! Notes\n\|}"		"starter": "Curate 1–10 specific recordings with artist, title, canonical YouTube embed URL and notes. Verify the exact recording's musical identity and local scene, not only its artist or URL metadata. Keep useful historical and live examples. For default listening, use the last ten years: popular music needs both recent original repertoire and recent recording; traditional/classical repertoire may be older but its recording must qualify. Uploads, remasters, compilations and later live versions do not reset the original popular repertoire date. Unknown dates remain unknown. Prefer a suitable prompt-start studio/official recording first; good live performances belong later in the playlist and must not be deleted simply for being live.\n\nThe listening profile describes how this genre is used. Repertoire is popular, traditional or classical. Field use is regional or context-only: broad umbrella/uncorroborated fields are contextual evidence and cannot establish local dominance. Explain this judgment in Notes. Neither field is an audience measurement.\n\n{\| class=\"wikitable\"\n\|+ MuGlobe listening profile\n! Repertoire !! Field use !! Notes\n\|}\n\nEach track has its own Repertoire kind (popular, traditional or classical); a genre may contain more than one. Dates preserve known precision: YYYY-MM-DD, YYYY-MM or YYYY; enter unknown otherwise. Format is audio, music-video, live or unknown. Opening is prompt, delayed or unknown; record actual evidence, never infer a prompt start solely from the format. Places use semicolon-separated country:Name or region:ID keys supported by the musical scene, not nationality or concert location alone. Fit is supported, pending or rejected. Evidence contains supporting HTTPS links; Review note explains what those sources establish and any limits. Supported means the specific recording was reviewed; oEmbed alone is insufficient. Add native footnotes in Notes for readers. The explicit compiler retains exact native revisions; ordinary builds never author content. Historical/undated examples remain separate from automatic contemporary listening.\n\n{\| class=\"wikitable muglobe-performances\"\n\|+ MuGlobe representative performances\n! Artist !! Performance / song / title !! Embedded player URL !! Notes !! Repertoire kind !! Repertoire date !! Recording date !! Format !! Opening !! Places !! Fit !! Evidence !! Review note\n\|}"
	},		},
	{		{
Line 80:		Line 80:
	}		}
	],		],
	"instructions": "Explain what listeners will hear, where the genre developed and where it is now adopted. Separate present-day listening from origins, and describe specific places and communities rather than assuming uniform national popularity. A historical genre may have limited present activity. Related genres is optional. Use sources and accessible musical examples. Hotspot mushrooms is the final section. Understand the connected musical landscape before choosing circles. Use nearby cities as clues to a wider region, not automatic isolated mushrooms. Include intervening countryside, distinguish meaningful detached scenes, and calibrate the fading field across the whole heartland. Centers need not be cities. Use the fewest useful broad fields, with concise Notes explaining editorial judgment. No source column or per-mushroom citation is required. Manual coordinates and explicit compilation remain in use. ~~Include 1–10 representative performances with credited artist~~, ~~performance~~/~~song/title, canonical embedded player URL and explanatory notes~~. ~~Prefer YouTube artist, broadcaster or institutional sources; cite~~ the ~~recording~~ and ~~contextual~~ evidence. ~~Playlist order follows table order. Existing articles migrate deliberately without altering their prose~~ or ~~mushrooms~~."		"instructions": "Explain what listeners will hear, where the genre developed and where it is now adopted. Separate present-day listening from origins, and describe specific places and communities rather than assuming uniform national popularity. A historical genre may have limited present activity. Related genres is optional. Use sources and accessible musical examples. Hotspot mushrooms is the final section. Understand the connected musical landscape before choosing circles. Use nearby cities as clues to a wider region, not automatic isolated mushrooms. Include intervening countryside, distinguish meaningful detached scenes, and calibrate the fading field across the whole heartland. Centers need not be cities. Use the fewest useful broad fields, with concise Notes explaining editorial judgment. No source column or per-mushroom citation is required. Manual coordinates and explicit compilation remain in use. Representative recordings follow the current listening editorial policy: verify the specific arrangement and local scene; record original repertoire and recording dates separately; contemporary default listening uses a rolling ten-year window. Keep historical examples separately and preserve good live recordings, sequencing a suitable prompt-start studio/official recording first. Use the required listening-profile and performance tables, with evidence and explicit uncertainty. Do not treat upload/reissue dates as recording dates or oEmbed metadata as musical proof."
	}		}

Edb: Add representative performance entries for wiki-driven genre playlists

2026-10-18T17:41:49Z

Add representative performance entries for wiki-driven genre playlists

muglobe-definition
← Older revision		Revision as of 17:41, 18 October 2026
Line 16:		Line 16:

	The retained article bibliography can support the broader narrative. Radius marks the zero edge of a linear fade; review the entire regional field rather than only its center. Coordinates remain manually authored and the compiler remains deterministic.		The retained article bibliography can support the broader narrative. Radius marks the zero edge of a linear fade; review the entire regional field rather than only its center. Coordinates remain manually authored and the compiler remains deterministic.

			Representative performances supplies the editable genre playlist. Each row contains artist, title, canonical YouTube embedded player URL and explanatory notes. Native citations document the recording and its relevance. Explicit compilation publishes validated entries to the globe; ordinary edits never regenerate map assets.
Line 2:		Line 2:
	"id": "genre",		"id": "genre",
	"label": "Genre",		"label": "Genre",
	"version": 8,		"version": 9,
	"published": true,		"published": true,
	"sections": [		"sections": [
Line 52:		Line 52:
	"requireContent": true,		"requireContent": true,
	"allowSubsections": true		"allowSubsections": true
			},
			{
			"key": "representative-performances",
			"label": "Representative performances",
			"level": 2,
			"required": true,
			"requireContent": true,
			"allowSubsections": true,
			"starter": "Curate 1–10 representative recordings, preferably from official artists, ensembles, broadcasters, archives or cultural institutions. Include living practice and useful historical examples where appropriate. Credit the actual performers; explain what to listen for and identify adaptations, excerpts or mixed-genre concerts. A studio recording or official music video is acceptable. Do not substitute search-result or playlist URLs for a specific performance.\n\nUse the four columns below. Embedded player URL must be a complete canonical HTTPS YouTube embed URL, for example https://www.youtube.com/embed/VIDEO_ID (replace VIDEO_ID with the real 11-character identifier). Do not paste iframe HTML or URL parameters. Add reliable native citations in Notes and include their reference list in the article. Keep rows in the preferred listening order. Wiki publication stores these entries; the explicit performance compiler validates them and publishes the globe playlist.\n\n{\| class=\"wikitable muglobe-performances\"\n\|+ MuGlobe representative performances\n! Artist !! Performance / song / title !! Embedded player URL !! Notes\n\|}"
	},		},
	{		{
Line 71:		Line 80:
	}		}
	],		],
	"instructions": "Explain what listeners will hear, where the genre developed and where it is now adopted. Separate present-day listening from origins, and describe specific places and communities rather than assuming uniform national popularity. A historical genre may have limited present activity. Related genres is optional. Use sources and accessible musical examples. Hotspot mushrooms is the final section. Understand the connected musical landscape before choosing circles. Use nearby cities as clues to a wider region, not automatic isolated mushrooms. Include intervening countryside, distinguish meaningful detached scenes, and calibrate the fading field across the whole heartland. Centers need not be cities. Use the fewest useful broad fields, with concise Notes explaining editorial judgment. No source column or per-mushroom citation is required. Manual coordinates and explicit compilation remain in use."		"instructions": "Explain what listeners will hear, where the genre developed and where it is now adopted. Separate present-day listening from origins, and describe specific places and communities rather than assuming uniform national popularity. A historical genre may have limited present activity. Related genres is optional. Use sources and accessible musical examples. Hotspot mushrooms is the final section. Understand the connected musical landscape before choosing circles. Use nearby cities as clues to a wider region, not automatic isolated mushrooms. Include intervening countryside, distinguish meaningful detached scenes, and calibrate the fading field across the whole heartland. Centers need not be cities. Use the fewest useful broad fields, with concise Notes explaining editorial judgment. No source column or per-mushroom citation is required. Manual coordinates and explicit compilation remain in use. Include 1–10 representative performances with credited artist, performance/song/title, canonical embedded player URL and explanatory notes. Prefer YouTube artist, broadcaster or institutional sources; cite the recording and contextual evidence. Playlist order follows table order. Existing articles migrate deliberately without altering their prose or mushrooms."
	}		}

Edb: Define mushrooms as inferred musical landscapes and remove Sources from the editable format; Ed’s direction

2026-10-18T00:02:54Z

Define mushrooms as inferred musical landscapes and remove Sources from the editable format; Ed’s direction

muglobe-definition
← Older revision		Revision as of 00:02, 18 October 2026
Line 13:		Line 13:
	These are editable editorial guidelines. Existing articles retain their recorded template version until deliberately migrated.		These are editable editorial guidelines. Existing articles retain their recorded template version until deliberately migrated.

	* '''Hotspot mushrooms:''' The final ~~required~~ section ~~contains~~ a ~~human~~-~~readable, variable-length wiki~~ table ~~defining the globe overlay. Its starting content explains~~ ID, ~~location~~, ~~decimal coordinates~~, ~~radius in kilometers~~, ~~strength~~, ~~notes~~ and ~~sources~~. ~~Editors can add~~, ~~remove~~ or ~~revise rows~~. The ~~explicit compiler reads an exact native wiki revision, validates~~ the ~~table~~ and ~~prepares~~ the ~~existing static globe database and fields~~.		* '''Hotspot mushrooms:''' The final section represents inferred musical landscapes, not a catalogue of cited cities. Its seven-column editable table contains ID, Location, Latitude, Longitude, Radius (km), Strength and Notes. Begin with regional understanding, synthesize varied perspectives and lived knowledge, then choose the fewest useful broad fields. Nearby strong cities generally indicate a connected heartland including intervening communities. Sources are not a field or a per-row publication gate.

			The retained article bibliography can support the broader narrative. Radius marks the zero edge of a linear fade; review the entire regional field rather than only its center. Coordinates remain manually authored and the compiler remains deterministic.
Line 2:		Line 2:
	"id": "genre",		"id": "genre",
	"label": "Genre",		"label": "Genre",
	"version": 7,		"version": 8,
	"published": true,		"published": true,
	"sections": [		"sections": [
Line 68:		Line 68:
	"requireContent": true,		"requireContent": true,
	"allowSubsections": true,		"allowSubsections": true,
	"starter": "~~Each row is~~ one ~~circular hotspot~~ mushroom ~~used by~~ the ~~globe~~. ~~Edit the table in the visual editor, or add/remove source rows~~. Location describes the ~~center~~; latitude and longitude are decimal degrees, with south/west negative. Radius is in kilometers (0.01 to 5,000)~~; strength is from 0 to 1. The~~ field ~~fades linearly to~~ zero at its ~~radius~~, ~~and overlapping~~ mushrooms of this genre combine by their strongest ~~value. These are editorial listening/activity illustrations, not measured audience percentages~~.\n\~~nKeep~~ each ~~existing~~ ID stable~~. Use~~ this genre's lowercase identifier followed by a ~~place~~ name~~, such as forro~~-~~recife. Give every row a location~~, ~~notes~~ and ~~at least one direct external source link~~. ~~Sources support~~ the ~~musical connection; they do not claim to measure the numerical~~ settings~~. Keep the table caption and column names. Do~~ not ~~leave example or empty rows~~. A deliberate ~~compilation publishes checked data to the globe; saving prose alone does not run it~~.\n\n{\| class=\"wikitable muglobe-hotspots\"\n\|+ MuGlobe hotspot mushrooms v1\n! ID !! Location !! Latitude !! Longitude !! Radius (km) !! Strength !! Notes ~~!! Sources~~\n\|}"		"starter": "Mushrooms describe our understanding of a musical landscape. Identify the broad heartland, connected communities and distinct adopted scenes first, then use the fewest useful circles to represent them. Nearby cities often sample one shared region: include the countryside and smaller communities between them instead of drawing a separate mushroom for every documented city. A center may lie between cities. Use Notes to explain the regional judgment.\n\nEach row defines one circular field. Location describes the represented area; latitude and longitude are decimal degrees, with south/west negative. Strength is from 0 to 1. Radius is in kilometers (0.01 to 5,000) and marks the distance where the field reaches zero, not the edge of a uniformly strong core. Make it large enough that the heartland and its intervening communities remain strong, then review transitions on the globe. Overlapping mushrooms of this genre combine by their strongest contribution.\n\nAdd, remove or revise ordinary table rows. Keep each surviving ID stable and use this genre's lowercase identifier followed by a descriptive region name. The table has no per-mushroom source requirement: it records informed judgment, experience and synthesis. Article references and broader research can explain the context. The numbers are editorial map settings, not listener percentages. Compilation remains a deliberate operation.\n\n{\| class=\"wikitable muglobe-hotspots\"\n\|+ MuGlobe hotspot mushrooms\n! ID !! Location !! Latitude !! Longitude !! Radius (km) !! Strength !! Notes\n\|}"
	}		}
	],		],
	"instructions": "Explain what listeners will hear, where the genre developed and where it is now adopted. Separate present-day listening from origins, and describe specific places and communities rather than assuming uniform national popularity. A historical genre may have limited present activity. Related genres is optional. Use sources and accessible musical examples. Hotspot mushrooms is the final section. ~~Its editable table defines~~ the ~~genre overlay; keep~~ the ~~supplied caption and column labels and cite~~ the ~~place/music relationship~~. ~~Numerical radius and strength are~~ editorial ~~settings~~. ~~Compilation~~ is an explicit ~~editorial operation~~."		"instructions": "Explain what listeners will hear, where the genre developed and where it is now adopted. Separate present-day listening from origins, and describe specific places and communities rather than assuming uniform national popularity. A historical genre may have limited present activity. Related genres is optional. Use sources and accessible musical examples. Hotspot mushrooms is the final section. Understand the connected musical landscape before choosing circles. Use nearby cities as clues to a wider region, not automatic isolated mushrooms. Include intervening countryside, distinguish meaningful detached scenes, and calibrate the fading field across the whole heartland. Centers need not be cities. Use the fewest useful broad fields, with concise Notes explaining editorial judgment. No source column or per-mushroom citation is required. Manual coordinates and explicit compilation remain in use."
	}		}

Edb: Add editable hotspot mushrooms table and starting content to Genre; authorized by Ed

2026-10-17T23:07:48Z

Add editable hotspot mushrooms table and starting content to Genre; authorized by Ed

muglobe-definition
← Older revision		Revision as of 23:07, 17 October 2026
Line 12:		Line 12:

	These are editable editorial guidelines. Existing articles retain their recorded template version until deliberately migrated.		These are editable editorial guidelines. Existing articles retain their recorded template version until deliberately migrated.

			* '''Hotspot mushrooms:''' The final required section contains a human-readable, variable-length wiki table defining the globe overlay. Its starting content explains ID, location, decimal coordinates, radius in kilometers, strength, notes and sources. Editors can add, remove or revise rows. The explicit compiler reads an exact native wiki revision, validates the table and prepares the existing static globe database and fields.
Line 2:		Line 2:
	"id": "genre",		"id": "genre",
	"label": "Genre",		"label": "Genre",
	"version": 6,		"version": 7,
	"published": true,		"published": true,
	"sections": [		"sections": [
Line 60:		Line 60:
	"requireContent": true,		"requireContent": true,
	"allowSubsections": true		"allowSubsections": true
			},
			{
			"key": "hotspot-mushrooms",
			"label": "Hotspot mushrooms",
			"level": 2,
			"required": true,
			"requireContent": true,
			"allowSubsections": true,
			"starter": "Each row is one circular hotspot mushroom used by the globe. Edit the table in the visual editor, or add/remove source rows. Location describes the center; latitude and longitude are decimal degrees, with south/west negative. Radius is in kilometers (0.01 to 5,000); strength is from 0 to 1. The field fades linearly to zero at its radius, and overlapping mushrooms of this genre combine by their strongest value. These are editorial listening/activity illustrations, not measured audience percentages.\n\nKeep each existing ID stable. Use this genre's lowercase identifier followed by a place name, such as forro-recife. Give every row a location, notes and at least one direct external source link. Sources support the musical connection; they do not claim to measure the numerical settings. Keep the table caption and column names. Do not leave example or empty rows. A deliberate compilation publishes checked data to the globe; saving prose alone does not run it.\n\n{\| class=\"wikitable muglobe-hotspots\"\n\|+ MuGlobe hotspot mushrooms v1\n! ID !! Location !! Latitude !! Longitude !! Radius (km) !! Strength !! Notes !! Sources\n\|}"
	}		}
	],		],
	"instructions": "Explain what listeners will hear, where the genre developed and where it is now adopted. Separate present-day listening from origins, and describe specific places and communities rather than assuming uniform national popularity. A historical genre may have limited present activity. Related genres is optional. Use sources and accessible musical examples."		"instructions": "Explain what listeners will hear, where the genre developed and where it is now adopted. Separate present-day listening from origins, and describe specific places and communities rather than assuming uniform national popularity. A historical genre may have limited present activity. Related genres is optional. Use sources and accessible musical examples. Hotspot mushrooms is the final section. Its editable table defines the genre overlay; keep the supplied caption and column labels and cite the place/music relationship. Numerical radius and strength are editorial settings. Compilation is an explicit editorial operation."
	}		}

Edb: AI-assisted first-pass outline from Ed's Country template, published at his request.

2026-10-17T22:37:09Z

AI-assisted first-pass outline from Ed's Country template, published at his request.

@@ Line 1: / Line 1: @@
-This template represents the '''Genre''' article category. Its editorial organization is awaiting definition by the superadministrator. It is not yet available for creating new articles.
+This is the published first-pass outline for '''Genre''' articles on MuGlobe.com, extrapolated from Ed's Country template at his request on October 17, 2026.
@@ Line 2: / Line 2: @@
 	"id": "genre",
 	"label": "Genre",
-	"version": 5,
+	"version": 6,
-	"published": false,
+	"published": true,
-	"sections": [],
+	"sections": [
 	"instructions": ""
+}

MuGlobe template setup: Restore current editorial template state after retaining historical snapshot

2026-10-17T20:33:06Z

Restore current editorial template state after retaining historical snapshot

@@ Line 2: / Line 2: @@
 	"id": "genre",
 	"label": "Genre",
-	"version": 4,
+	"version": 5,
-	"published": true,
+	"published": false,
-	"sections": [
+	"sections": [],
 	"instructions": ""
+}