In every TAME module, there can be a section called a header that describes metadata related to the module, or additional instructions for the engine to follow. This is represented in TAMEScript as a section called "module" that is a series of key-value pairs.

	module
	{
		key = [VALUE];
		...
	}

All header values are stored as strings in the module - if they are read with a utility or retrieved in the module via the command header(), it is returned as a string. The programs or implementations that read them can convert them to an expected type, though - if the value associated with the key is supposed to be an integer, TAME will try to parse it as one.

A sample module header would look like:

	module
	{
		title = "A Sample Module";
		author = "Matthew Tropiano";
		email = "matttropiano@email.net";
		web = "https://tame-if.com";
		twitter = "@ModuleMaker";
		ifid = "12345678-ABCD-EF90-1234-567890ABCDEF";
	}

Since the TAME header can contain any kind of metadata for modules, the following keys are considered standardized for most systems that wish to use module metadata in a meaningful way (this may change over time as more changes/standards are proposed):

Although headers are intended to be purely informational, there are a few headers intended to be read by TAME implementations in order to alter certain run-time behavior. These key/value pairs are considered optional, but they MUST be supported by certified implementations of TAME. The defaults listed MUST be the accepted values if the keys are missing or the values are invalid or not able to be parsed.

The following are header keys that influence TAME: